From owner-freebsd-current Tue Mar 25 7: 4:12 2003 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 5483D37B401 for ; Tue, 25 Mar 2003 07:04:10 -0800 (PST) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C29F43F93 for ; Tue, 25 Mar 2003 07:04:09 -0800 (PST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost.kawo2.rwth-aachen.de [127.0.0.1]) by fump.kawo2.rwth-aachen.de (8.12.8/8.12.6) with ESMTP id h2PF48Mf007626; Tue, 25 Mar 2003 16:04:08 +0100 (CET) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.8/8.12.6/Submit) id h2PF47Qx007625; Tue, 25 Mar 2003 16:04:07 +0100 (CET) Date: Tue, 25 Mar 2003 16:04:07 +0100 From: Alexander Langer To: Terry Lambert Cc: current@FreeBSD.org Subject: Re: several background fsck panics Message-ID: <20030325150407.GG1700@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , Terry Lambert , current@FreeBSD.org References: <20030324215712.GA844@fump.kawo2.rwth-aachen.de> <3E7FE3CE.ECD2775F@mindspring.com> <20030325110843.GF1700@fump.kawo2.rwth-aachen.de> <3E804392.40844D63@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E804392.40844D63@mindspring.com> X-PGP-Fingerprint: 7EC1 5B98 4554 2A63 9079 2B2F 9A94 CD6F 7F14 EFA4 X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. User-Agent: Mutt/1.5.3i X-Spam-Status: No, hits=-20.8 required=5.0 tests=AWL,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Terry Lambert (tlambert2@mindspring.com): > A manual fsck can deal with corrupt data. [...] Yes, I recall the discussion about WC on ata vs. softupdates a few months back. I even have it disabled on more important machines than this one :-) > The panic was not, in fact, a result of the background fsck > itself: it was a result of an attempt to access FS structures > by the kernel through the FS, assuming -- incorrectly -- that > the FS structures were in a self-consistent state. Actually I don't care _where_ the panic happened. If I hadn't manually interupted the boot process, this kernel would have booted and paniced on that error for the next three years. I could fix that by simply doing a manual (background_fsck=NO), so something is "broken", for some definition of broken: If my system panics, I call that "broken". We claim background fsck as a "cool new" feature in the release notes, which is even the DEFAULT, including WC on ATA disks, which is ALSO the default. So , and if this is broken, there is a serious design flaw, which must be fixed. It doesn't help to explain why the error is there, the next user will have the same error, running a verbatim system. Ciao Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message