Date: Wed, 29 Mar 2006 19:27:12 +0200 From: Peter Holm <peter@holm.cc> To: Suleiman Souhlal <ssouhlal@FreeBSD.org> Cc: current@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Fun with df Message-ID: <20060329172712.GA48623@peter.osted.lan> In-Reply-To: <442A8D86.9010903@FreeBSD.org> References: <20060328155316.GA20036@peter.osted.lan> <20060328180553.GA8364@xor.obsecurity.org> <442A8D86.9010903@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 29, 2006 at 03:37:10PM +0200, Suleiman Souhlal wrote: > Kris Kennaway wrote: > >On Tue, Mar 28, 2006 at 05:53:16PM +0200, Peter Holm wrote: > > > >>I've seen this problem on both RELENG_6 from Mar 27 19:37 UTC and HEAD: > > > > > >Have you figured out how to cause it? I and others see it > >occasionally (also things like this at reboot: > > > >/c: unmount pending error: blocks -68512 files 0 > > > >which dates back at least to 5.3). But I haven't been able to figure > >out how to trigger it on demand. > > IIRC it's pretty easy to trigger: delete a lot of files, and unmount > right after as rm is done. > umount -f in the middle of the rm might also work. > Yes! I created a few hundred thousand empty files, umount + fsck + mount without any problems. The df corruption started the moment I began deleting the files. The following umount gave this warning: /tmp: unmount pending error: blocks 4137248 files 0 - Peter > -- Suleiman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060329172712.GA48623>