From owner-freebsd-arch Sun Apr 1 8:25:18 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 4AFE637B719 for ; Sun, 1 Apr 2001 08:25:16 -0700 (PDT) (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 f31FP2h74091; Sun, 1 Apr 2001 11:25:03 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 1 Apr 2001 11:25:02 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kirk McKusick Cc: arch@freebsd.org Subject: Re: Background Fsck In-Reply-To: <200103290522.VAA06966@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 On Wed, 28 Mar 2001, Kirk McKusick wrote: > The implementation will be to add a new option, -B, to the front end, > fsck. The startup scripts will invoke fsck twice, once at the current > location without -B to do all the foreground checks, and once towards > the end of the startup script with -B to start the background checks. On further thought, I'd like to propose the following alternative behavior: fsck -F # perform foreground checks fsck -B # perform background checks fsck # perform all checks I.e., the rc scripts will invoke first using fsck -F, then fsck -B (feel free to twiddle letters here). However, if a user simply invokes fsck by itself (or with other arguments, such as -p) in single-user mode, the full checks will be done. This preserves the sanity of long-lasting documentation that indicates simply running fsck or fsck -p on hitting single-user-mode is sufficient to restore a file system to normal functionality. In this way, it's possible also for the default behavior without special flags to block until the file systems are ready, the currently expected behavior. It's possible I'm misunderstanding an aspect of the way you've described a flags that makes my suggestion redundant, if so, let me know :-). 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