Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: find . -name '*.req' -mtime +2 -exec rm {} \; not deleting files
Operating Systems Linux Red Hat find . -name '*.req' -mtime +2 -exec rm {} \; not deleting files Post 302726649 by chebarbudo on Monday 5th of November 2012 03:48:52 AM
Old 11-05-2012
Hey rehantayyab82,

If the find takes a long time just to show files, my guess is that you directory is big.

There may be a race condition as well. Some file looks like they disappear between the time they're detected by find and deleted by rm (so the warning).

How big is a req file on average. Maybe you cannot expect your operation to free much space.

Good luck
Santiago
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

(Req)Shell script req

HI All Im new to shell scripting...kindly plz help me... I need a shell script for: We have to take export of all db's on daily basis from all svr's and keep these export backups on diffrent server. Plz help. Regards Gaurav (5 Replies)
Discussion started by: ergauravtaneja
5 Replies

2. Shell Programming and Scripting

Deleting files using find command

I want to find the files and delete all the files except the last file. I am using find command , I am sending the find output to a file and getting all the lines except the last one and sending it to the remove command . This is not working. can anyone help me out to do it in the find command... (8 Replies)
Discussion started by: deepaklanka
8 Replies

3. Shell Programming and Scripting

deleting files inside shell script - ( using find)

Hi, I am using the command find /apps/qualdb/gpcn/scripts/cab_outbound/archive -name 'z*' -mtime +28 -exec rm {} \; in unix command prompt for deleting the files in my unix system under the specfied folder. It was succesfull. But when i running this command inside a shell script name... (2 Replies)
Discussion started by: Jayaram.Nambura
2 Replies

4. UNIX for Dummies Questions & Answers

(find) mtime vs. (unix) mtime

Hi I've made some test with perl script to learn more about mtime... So, my question is : Why the mtime from findfind /usr/local/sbin -ctime -1 -mtime -1 \( -name "*.log" -o -name "*.gz" \) -print are not the same as mtime from unix/linux in ls -ltr or in stat() function in perl : stat -... (2 Replies)
Discussion started by: hiddenshadow
2 Replies

5. UNIX for Dummies Questions & Answers

Req 1-liner for Awk, et al to find str position

Hi, I'm trying to find the position of a series of numbers within a large text file. The numbers are separated by spaces. This works fine: type Huge_File.txt | gawk "{print index($0,"255")}" But this does not: type Huge_File.txt | gawk "{print index($0,"188 028 239 160 016 190 137... (4 Replies)
Discussion started by: Lemming42
4 Replies

6. Shell Programming and Scripting

Help on find -mtime -exec

Hello people. Part of my script: echo "Compressing files older than 2 months in ${TEMP_DIR} directory ..." find ${DATA_DIR}/ -name '*.dat' -mtime 61 -exec compress {} \; #BELOW COMMAND DOES NOT WORK :-( <<<<<<----------- find ${DATA_DIR}/ -name '*.o.lines.*' -mtime 61 -exec compress {}... (2 Replies)
Discussion started by: drbiloukos
2 Replies

7. UNIX for Dummies Questions & Answers

Find using mtime

Hi, so I was using mtime and its not behaving the way I would think its supposed too. I have two pdf files. One modified today and another 6 months ago. I upload them to the solaris server. Then I run the below find statements. This finds my 2 files find *.pdf -type f -name '*.pdf' this finds... (2 Replies)
Discussion started by: vsekvsek
2 Replies

8. Shell Programming and Scripting

Find by name and mtime

Hi, I'm trying to find all files that have a .ksh and .p extension and that are 7 days old by using the below find command but it doesn't seem to as expected. It gives me random results.. Can someone point out what may be wrong? find . -name "*.ksh" -o -name "*.p" -mtime -7 (2 Replies)
Discussion started by: Jazmania
2 Replies

9. Red Hat

Deleting using "find -mtime" not working

This command used to work in my old Linux servers to delete old files (older than 2 days, in this case) but it suddenly not working at all-- find /path/to/dir/* -mtime 2 -exec rm {} \; Anything I am missing? Would appreciate any tips. Thanks! (6 Replies)
Discussion started by: pkiula
6 Replies

10. Shell Programming and Scripting

[Solved] Issue with deleting files through find

Hi, I have a script similar to this #!/bin/ksh cd /orcl/bir/eod_badfiles find ./ -type f -name "*.csv" -mtime +6 -exec rm -f {} \; find ./ -type f -name "*.bad" -mtime +6 -exec rm -f {} \; cd /orcl/bir find ./ -type f -name "*.log" -mtime +6 -exec rm -f {} \; This was working fine in one... (5 Replies)
Discussion started by: Gangadhar Reddy
5 Replies

LEARN ABOUT DEBIAN

mhddfs

mhddfs(1)						      General Commands Manual							 mhddfs(1)

NAME

       mhddfs - The driver combines a several mount points into the single one.

SYNOPSIS

	mhddfs /dir1,/dir2[,/path/to/dir3] /path/to/mount [-o options]
	mhddfs /dir1 dir2,dir3 /mount/point [-o options]
	...
	fusermount -u /path/to/mount

   fstab record example:
       mhddfs#/path/to/dir1,/path/to/dir2 /mnt/point fuse defaults 0 0

       mhddfs#/dir1,/dir2,/dir3 /mnt fuse logfile=/var/log/mhddfs.log 0 0

OPTIONS

       with an -o option1,option2...  you can specify some additional options:

   logfile=/path/to/file.log
       specify a file that will contain debug information.

   loglevel=x
       0 - debug messages

       1 - info messages

       2 - standard (default) messages

   mlimit=size[m|k|g]
       a  free space size threshold If a drive has the free space less than the threshold specifed then another drive will be choosen while creat-
       ing a new file.	If all the drives have free space less than the threshold specified then a  drive  containing  most  free  space  will	be
       choosen.

       Default value is 4G, minimum value is 100M.

       This option accepts suffixes:
	      [mM] - megabytes

	      [gG] - gigabytes

	      [kK] - kilobytes

       For an information about the additional options see output of:
	      mhddfs -h

DESCRIPTION

       The  file  system  allows to unite a several mount points (or directories) to the single one. So a one big filesystem is simulated and this
       makes it possible to combine a several hard drives or network file systems. This system is like unionfs but it can choose a drive with  the
       most of free space, and move the data between drives transparently for the applications.

       While writing files they are written to a 1st hdd until the hdd has the free space (see mlimit option), then they are written on a 2nd hdd,
       then to 3rd etc.

       df will show a total statistics of all filesystems like there is a big one hdd.

       If an overflow arises while writing to the hdd1 then a file content already written will be transferred to a hdd containing enough of  free
       space  for a file. The transferring is processed on-the-fly, fully transparent for the application that is writing. So this behaviour simu-
       lates a big file system.

   WARNINGS
       The filesystems are combined must provide a possibility to get their parameters correctly (e.g. size of free space). Otherwise the  writing
       failure can occur (but data consistency will be ok anyway). For example it is a bad idea to combine a several sshfs systems together.

       Please read FUSE documentation for a further conception.

COPYRIGHT

       Distributed under GPLv3

       Copyright (C) 2008 Dmitry E. Oboukhov <dimka@avanto.org>

								   February 2008							 mhddfs(1)
All times are GMT -4. The time now is 07:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy