From owner-freebsd-arch Fri Mar 30 6: 5:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 94C0237B71B for ; Fri, 30 Mar 2001 06:05:23 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2UE5Ah40563; Fri, 30 Mar 2001 09:05:10 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 30 Mar 2001 09:05:10 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kirk McKusick Cc: arch@freebsd.org Subject: Re: Background Fsck In-Reply-To: <200103300558.VAA09201@beastie.mckusick.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk, I haven't had a chance to look at the tunefs source lately, but quick question: does tunefs block the setting of the soft updates flag on a dirty file system? It seems to me that, if it doesn't, a possible nasty sequence of events is: system does unclean shutdown without soft updates, administrator (possibly not realizing this) boots to single-user mode, and sets soft updates, then attempts to enter multi-user mode, where fsck says "ah, soft updates, doesn't matter if it's unclean, let's background fsck". Shortly thereafter, an inconsistency is discovered and the system panics. As such, tunefs should only allow the setting of soft updates on a file system marked clean. It may already do this, but figured I should ask. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message