From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 00:16:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7385A1065688 for ; Mon, 22 Sep 2008 00:16:45 +0000 (UTC) (envelope-from clint@0lsen.net) Received: from belle.0lsen.net (belle.0lsen.net [75.150.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 5462C8FC13 for ; Mon, 22 Sep 2008 00:16:45 +0000 (UTC) (envelope-from clint@0lsen.net) Received: by belle.0lsen.net (Postfix, from userid 1001) id D3C8B79675; Sun, 21 Sep 2008 16:59:50 -0700 (PDT) Date: Sun, 21 Sep 2008 16:59:50 -0700 From: Clint Olsen To: Jeremy Chadwick Message-ID: <20080921235950.GB25826@0lsen.net> References: <20080921213426.GA13923@0lsen.net> <20080921215203.GC9494@icarus.home.lan> <20080921215930.GA25826@0lsen.net> <20080921220720.GA9847@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080921220720.GA9847@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Organization: NULlsen Network X-Disclaimer: Mutt Bites! X-0lsen-net-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: D3C8B79675.42A62 X-0lsen-net-MailScanner: Found to be clean X-0lsen-net-MailScanner-From: clint@0lsen.net X-Spam-Status: No Cc: freebsd-stable@freebsd.org Subject: Re: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2008 00:16:45 -0000 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.