Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Sep 1999 13:00:50 -0500 (CDT)
From:      David Scheidt <dscheidt@enteract.com>
To:        Zhihui Zhang <zzhang@cs.binghamton.edu>
Cc:        Luoqi Chen <luoqi@watermarkgroup.com>, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject:   Re:  The usage of MNT_RELOAD
Message-ID:  <Pine.NEB.3.96.990908125631.44707B-100000@shell-2.enteract.com>
In-Reply-To: <Pine.GSO.3.96.990908133020.21415B-100000@sol.cs.binghamton.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.990908125631.44707B-100000>