> On Thu, 02 Aug 2001 10:42:29 +0100, Brian Somers wrote:
> > If the error keeps turning up, I would guess that you have a 0 or
> > empty fsck field in /etc/fstab and fsck -s therefore not fixing the
> > problem.
> Nope. I have passno set for the filesystem on which I also see this. I
> used to have background fsck enabled, but I disabled it because of
> horrid unkillable fsck behaviour. Perhaps background fsck did something
> nasty to my filesystem that normal fsck isn't seeing?
The soft-updates code stores two block counts and two file counts in the
superblock so that df(1) can give sane answers for filesystems where
soft-updates is enabled.
fsck(8) fixes them up (and frees off the bitmaps etc) on my machines
Brian <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour ! <brian@[uk.]OpenBSD.org>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message