Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Nov 2006 14:19:40 -0600
From:      "Matthew D. Fuller" <fullermd@over-yonder.net>
To:        Peter Jeremy <peterjeremy@optushome.com.au>
Cc:        ohartman@mail.zedat.fu-berlin.de, freebsd-stable@freebsd.org
Subject:   Re: Problems unmounting/fssyncking extern UFS filesystem
Message-ID:  <20061127201940.GD31944@over-yonder.net>
In-Reply-To: <20061127183758.GC865@turion.vk2pj.dyndns.org>
References:  <200611271353.kARDr6tN034491@lurza.secnetix.de> <20061127164119.E63DB45054@ptavv.es.net> <20061127183758.GC865@turion.vk2pj.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 28, 2006 at 05:37:58AM +1100 I heard the voice of
Peter Jeremy, and lo! it spake thus:
> 
> All current Un*x filesystems will automatically flush all buffers as
> part of the unmount process

That Depends(tm), partly on what you mean by 'unmount'.

With my Nov05 and Jun06 -CURRENT's, I had to take great care to sync
and sync and wait and sync and sync filesystems before "mount -u -o
ro"'ing them, because otherwise they'd end up NOT flushing everything,
leaving unreferenced stuff around that fsck had to clean up, but only
if I ran it manually because mount DID mark the filesystem as clean.

I just tried to reproduce it on my last-week -CURRENT, and it no
longer does that.  Instead, it locked itself into a "softdep_waitidle:
Failed to flush worklist" loop and won't LET me remount r/o (or
unmount) the filesystems.  Obviously, I should have kept up my
now-established habit of sync'ing and waiting a while before
un/remounting...


-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.



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