Date: Tue, 11 Mar 1997 13:44:10 -0500 (EST) From: John Fieber <jfieber@indiana.edu> To: Terry Lambert <terry@lambert.org> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, mrcpu@cdsnet.net, hackers@FreeBSD.ORG Subject: Re: Maybe a showstopper, maybe not. Message-ID: <Pine.BSF.3.95q.970311132643.26807D-100000@fallout.campusview.indiana.edu> In-Reply-To: <199703111811.LAA25726@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 11 Mar 1997, Terry Lambert wrote: > > > 2.2 branch. The situation is a Solaris client mounting a disk > > > from my FreeBSD box. On a large directory tree, doing an `rm -r' > > > on the Solaris box misses files. It takes multiple invocations > > > of `rm -r' to actually clean everything out. > > > > That's truly bizarre. Do these "undeleted" files have *anything* > > in common, so far as you can make out? > > They remain after an "rm -f"? Yes. Okay, I unpacked a tarfile with about 600 files in a directory tree. find -name "*" gives the same results on my box and the solaris box. An rm -rf on the solaris box removes about 500 of the 600 files. Comparing the before and after lists as generated by find reveals that the rm only removes the first 27 +/- 1 files from a directory! Since there were no directories with > 2*27 files, a second rm -rf pass cleared everything out. Next, on a DEC box (OSF1 V4.0), the rm -rf works fine *but* the find command misses files in the same way that rm on solaris does, except the magic number is 40 +/- 1 per directory instead of 27. -john
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970311132643.26807D-100000>