Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Mar 2006 08:55:57 -0700
From:      Scott Long <scottl@samsco.org>
To:        Suleiman Souhlal <ssouhlal@freebsd.org>
Cc:        current@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: Fun with df
Message-ID:  <442AAE0D.2080608@samsco.org>
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
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.
> 
> -- Suleiman

So does this mean that dirty metadata buffers didn't get flushed?  If
so, where did they go?  Or does it mean that certain metadata fields
never even got updated?  Sigh, what a mess =-(  Does this happen with
softupdates turned off?

Scott




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442AAE0D.2080608>