UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY

[Jeremy Chadwick]

On Sun, Sep 21, 2008 at 02:59:30PM -0700, Clint Olsen wrote:
> I ran in multi-user mode because the system booted.  I figured that it
> would have halted the boot if it was serious enough to warrant single-user
> mode fsck.  That has happened before.
> 
> Thanks,
>
> -Clint
> 
> On Sep 21, Jeremy Chadwick wrote:
> > Are you running fsck on the filesystem while its mounted?  Are you doing
> > this in single-user or multi-user mode?

Re-adding mailing list to the CC list.

No, I don't think that is the case, assuming the filesystems are UFS2
and are using softupdates.  When booting multi-user, fsck is run in the
background, meaning the system is fully up + usable even before the fsck
has started.

Consider using background_fsck="no" in /etc/rc.conf if you prefer the
old behaviour.  Otherwise, boot single-user then do the fsck.

You could also consider using clri(8) to clear the inode (190).  Do this
in single-user while the filesystem is not mounted.  After using clri,
run fsck a couple times.

Also, are there any kernel messages about ATA/SCSI disk errors or other
anomalies?

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |