Date: Sun, 21 Sep 2008 16:59:50 -0700 From: Clint Olsen <clint.olsen@gmail.com> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY Message-ID: <20080921235950.GB25826@0lsen.net> In-Reply-To: <20080921220720.GA9847@icarus.home.lan> References: <20080921213426.GA13923@0lsen.net> <20080921215203.GC9494@icarus.home.lan> <20080921215930.GA25826@0lsen.net> <20080921220720.GA9847@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 21, Jeremy Chadwick wrote: > 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. The last time things crashed hard, the boot sequence was halted in order to run fsck. > Consider using background_fsck="no" in /etc/rc.conf if you prefer the > old behaviour. Otherwise, boot single-user then do the fsck. Yes, I'll do this. > 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. Ok, thanks. > Also, are there any kernel messages about ATA/SCSI disk errors or other > anomalies? None. In fact smartctl will not do anything now. It just prints out the quick banner message and exits immediately with no error. -Clint -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080921235950.GB25826>