Date: Wed, 8 Sep 1999 11:11:12 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: David Scheidt <dscheidt@enteract.com> Cc: Zhihui Zhang <zzhang@cs.binghamton.edu>, Luoqi Chen <luoqi@watermarkgroup.com>, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: The usage of MNT_RELOAD Message-ID: <199909081811.LAA88623@apollo.backplane.com> References: <Pine.NEB.3.96.990908125631.44707B-100000@shell-2.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> 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
The root filesystem is mounted *READ-ONLY* initially. fsck is then
run on all filesystems. Once fsck is done the root filesystem is
remounted R/W and the remaining filesystems are mounted R/W.
It's relatively safe to run fsck on a filesytem which has been mounted
read-only. It is not safe to run fsck on a filesystem which has been
mounted R/W.
It is best, of course, to run fsck only on filesystems that have not
been mounted but this cannot be done for the root filesystem for obvious
reasons, hence the read-only mount + fsck + remount R/W.
-Matt
Matthew Dillon
<dillon@backplane.com>
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?199909081811.LAA88623>