From owner-freebsd-current@FreeBSD.ORG Wed Mar 26 07:48:52 2003 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 1426A37B404 for ; Wed, 26 Mar 2003 07:48:52 -0800 (PST) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E72F43F93 for ; Wed, 26 Mar 2003 07:48:51 -0800 (PST) (envelope-from msch@snafu.de) Received: from tc01-n71-238.de.inter.net ([213.73.71.238] helo=current.best-eng.de) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 18yD90-000061-00 for freebsd-current@freebsd.org; Wed, 26 Mar 2003 16:48:50 +0100 Content-Type: text/plain; charset="us-ascii" From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: freebsd-current@freebsd.org Date: Wed, 26 Mar 2003 16:48:49 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200303261648.49512.msch@snafu.de> X-Spam-Status: No, hits=-15.5 required=5.0 tests=EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Re: several background fsck panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 15:48:53 -0000 Terry Lambert wrote: > The issue with the repeating background fsck's is important. > I suggest a counter that gets reset to zero each time the > FS is marked clean by fsck, and incremented each time the > background fsck process is started. > When this counter reaches a predefined value (I sugest a > command line option to background fsck, which defaults to > "3", if left unspecified), then the fsck is automatically > converted to a foreground fsck. > This counter would be recorded in the superblock. This sounds like a good idea! I vote for a counter of "2"... :-) Also I suggest to mention as clearly as possible, that operating Soft Updates with Write Cache enabled is kind of 'out of specs'. This cannot work when crashing! (As you stated clearly!) So I'm also voting for 'WC disable' for any kind of disks. SCSI-disks don't need it because of Tagged Queuing and only those ATA-Disks that *have* TQ can/should be operated 'the fast way' - hoping that Soeren gets it working again... :-/ -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT