Softupdates not preventing lengthy fsck

[Dan Nelson]

In the last episode (Apr 11), Kris Kennaway said:
> I'm seeing the following problem: on 6.0 machines which have had a lot
> of FS activity in the past but are currently quiet, an unclean reboot
> will require an hour or more of fscking and will end up clearing
> thousands of inodes:

This might be expected behaviour if the previous boot tried to do a
bgfsck and failed.  It should set a flag forcing a full fsck on the
next boot, which will clear out the half-committed inodes from the
previous crash.  I see it often on 5.*.

-- 
	Dan Nelson
	dnelson at allantgroup.com