From owner-freebsd-current@FreeBSD.ORG Wed Nov 24 11:49:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 366BD16A4CE; Wed, 24 Nov 2004 11:49:12 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8358B43D55; Wed, 24 Nov 2004 11:49:11 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])84DEF499E7; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14921-04; Wed, 24 Nov 2004 12:49:10 +0100 (CET) Received: from m2a2.dyndns.org (p548546B7.dip.t-dialin.net [84.133.70.183]) B8EED498E5; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 122B8D3F13; Wed, 24 Nov 2004 12:49:09 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17611-02; Wed, 24 Nov 2004 12:49:08 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 5789DCDA72; Wed, 24 Nov 2004 12:49:08 +0100 (CET) To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) From: Matthias Andree Date: Wed, 24 Nov 2004 12:49:08 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: 5-STABLE softupdates issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 11:49:12 -0000 Greetings, out of fun and to investigate claims about alleged bgfsck resource hogging (which I could not reproduce) posted to news:de.comp.os.unix.bsd, I pressed the reset button on a live FreeBSD 5-STABLE system. Upon reboot, fsck -p complained about an unexpected softupdates inconsistency on the / file system and put me into single user mode, the manual fsck / then asked me to agree to increasing a link count from 21 to 22 (and later to fix the summary, which I consider a non-issue). A subsequent fsck -p / ended with no abnormality detected. Unfortunately, I haven't copied the details, assuming they would be copied into the log, but they haven't. Is this a situation the current 5-STABLE softupdates code (on a UFS1 FS that I kept from FreeBSD 4) is allowed to cause? Is that a bug in the file system, say, write ordering goofed up? Or is that a bug in the firmware of my disk drive (Western Digital Caviar AC420400D, a rebranded IBM DJNA drive)? I gather that ATA drives are supposed to flush their caches on software (command) and hardware resets (reset line active). I did not power cycle. -- Matthias Andree