From owner-freebsd-hackers Tue Mar 11 10:45:36 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA28837 for hackers-outgoing; Tue, 11 Mar 1997 10:45:36 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28827 for ; Tue, 11 Mar 1997 10:45:29 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id NAA28346; Tue, 11 Mar 1997 13:44:11 -0500 (EST) Date: Tue, 11 Mar 1997 13:44:10 -0500 (EST) From: John Fieber To: Terry Lambert cc: "Jordan K. Hubbard" , mrcpu@cdsnet.net, hackers@FreeBSD.ORG Subject: Re: Maybe a showstopper, maybe not. In-Reply-To: <199703111811.LAA25726@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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