From owner-freebsd-hackers Wed Sep 8 11: 1:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id F363214DD7 for ; Wed, 8 Sep 1999 11:01:44 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 97521 invoked from network); 8 Sep 1999 18:00:50 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 8 Sep 1999 18:00:50 -0000 Date: Wed, 8 Sep 1999 13:00:50 -0500 (CDT) From: David Scheidt To: Zhihui Zhang Cc: Luoqi Chen , freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Sep 1999, Zhihui Zhang wrote: > > On Wed, 8 Sep 1999, Luoqi Chen wrote: > > > It is created almost exclusively for fsck (and similar programs) to update > > the in core image of the superblock (of / in single user mode) after the > > on disk version has been modified. > > > > Does fsck have to run on a MOUNTED filesystem? If so, your answer makes > sense to me: if fsck modifies the on-disk copy of the superblock, it does > not have to unmount and then remount the filesystem, it only need to > reload the superlock for disk. The root filesystem is mounted when it is fscked, as it is difficult to run fsck, which lives on the root filesystem, without mounting the root filesystem. You shouldn't run fsck on a mounted filesystem, except for this. The results are generally not fun. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message