Subject: Re: fsck_lfs leaves unclean filesystem
To: None <firstname.lastname@example.org>
From: Daniel Carosone <email@example.com>
Date: 11/20/2006 15:00:33
Content-Type: text/plain; charset=us-ascii
On Mon, Nov 20, 2006 at 12:30:47PM +1100, Daniel Carosone wrote:
> After the reboot and automatic fsck -p, in the first instance, the
> cleaner wasn't making forward progress, and wasn't recovering the
> space. I shut the domain down again and forced a full fsck. This
> found the unlinked file and cleaned it up - but left damage of its
> own. A second run fixed that.
> After a reboot and mount, the fs is still 107% full.. but the cleaner
> seems to be slowly trickling the space back.
No, it was worse than that.
The cleaner made a tiny amount of progress, then apparently got stuck
cleaning the same segs over and over again, each time thinking it had
So I shut down again, and fsck -f found the same "properly orphaned
inodes" that had been removed previously back again.
putting a "reboot" between each fsck run didn't help - but putting an
"xm destroy" (or presumably, a "reboot -n") between each run did work.
So it seems that, even with / mounted read only, reboot is causing the
filesystem to be closed in a way that is restoring the problems fsck
NetBSD nblfs 4.99.3 NetBSD 4.99.3 (XEN3_DOMU) #37: Tue Nov 14 20:51:10 EST =
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)
-----END PGP SIGNATURE-----