Date: Mon, 6 May 1996 11:30:06 -0600 From: Nate Williams <nate@sri.MT.net> To: John Capo <jc@irbs.com> Cc: freebsd-stable@freebsd.org Subject: Re: FS corruption during rm -fr Message-ID: <199605061730.LAA18033@rocky.sri.MT.net> In-Reply-To: <199605042232.SAA09640@irbs.irbs.com> References: <199605042232.SAA09640@irbs.irbs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> play/stable: > total 2 > drwxr-xr-x 3 root wheel 512 May 4 15:47 . > drwxr-xr-x 3 root wheel 512 May 4 15:48 .. > irbs 2# rm -fr play > rm: play/stable: Directory not empty > rm: play: Directory not empty > > > The same type of corruption has happened 5 times in the last 2 > days. Always during a rm -fr on a directory tree checked out of > cvs. Several passes are needed to get the FS clean again. I see this *all* the time on many systems (IDE and SCSI). I'm not sure why, but it appears to be related to CVS, since it's only the CVS directories that appear to get messed up. An easy way to recreate this bug is to check out the world, and then remove it all. It will *always* leave at least one or two directories that an un-removable. 3 passes of fsck in single-user mode are necessary to clean this up, at which point I can # cd /usr/lost+found;rm -rf * To clean it up, and then reboot and all will be well until I no longer unmount the FS cleanly (laptop patches) when the directories will show up again. > The system is a 486/66 with an Adaptec 1542B that I have been using > since 0.1 days and it has always been rock solid. The kernel is > pretty much stock -stable. The only difference in this kernel and > the ones I have run for the last 4 months is DDB and KTRACE. This > is the first -stable kernel I have run with those options. I've seen this with/without DDB and KTRACE. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605061730.LAA18033>