Date: Sun, 08 Dec 2002 20:48:24 -0800 From: Kirk McKusick <mckusick@beastie.mckusick.com> To: Archie Cobbs <archie@dellroad.org> Cc: Bruce Evans <bde@zeta.org.au>, Julian Elischer <julian@elischer.org>, freebsd-current@FreeBSD.ORG, Thomas-Henning von Kamptz <tomsoft@FreeBSD.ORG> Subject: Re: backgroud fsck is still locking up system (fwd) Message-ID: <200212090448.gB94mO59099523@beastie.mckusick.com> In-Reply-To: Your message of "Sun, 08 Dec 2002 17:03:43 PST." <200212090103.gB913hXV076280@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In theory the MNT_RELOAD command should reload all the filesystem metadata properly though this feature has not been tested with growfs. If anyone has the time to try it out and report back any problems, that would be appreciated. Kirk McKusick =-=-=-=-= From: Archie Cobbs <archie@dellroad.org> Subject: Re: backgroud fsck is still locking up system (fwd) In-Reply-To: <20021208083912.G14505-100000@gamplex.bde.org> To: Bruce Evans <bde@zeta.org.au> Date: Sun, 8 Dec 2002 17:03:43 -0800 (PST) CC: Archie Cobbs <archie@dellroad.org>, Kirk McKusick <mckusick@beastie.mckusick.com>, Julian Elischer <julian@elischer.org>, freebsd-current@FreeBSD.ORG, Thomas-Henning von Kamptz <tomsoft@FreeBSD.ORG> X-ASK-Info: Whitelist match Bruce Evans wrote: > > > Er, it should be obvious that growfs can't reasonably work on the mounted > > > partitions. growfs.1 doesn't exist, but growfs.8 already has the warning > > > in a general form: > > > > > > .... Currently growfs can only enlarge unmounted file systems. Do not > > > try enlarging a mounted file system, your system may panic and you will > > > not be able to use the file system any longer... > > > > Well, I suspected that it might not work... but I would disagree that it > > was *obvious* that it would not work. This was before "mount" had been > > run, so / was supposedly mounted (?) read-only. > > Perhaps the unobvious point is that fsck could work. If the mount is r/w, > then neither growfs nor fsck can even open the partition r/w. fsck somehow > works in the case of a r/o root, but growfs apparently doesn't. I think > fsck depends on no other processes making (significant) vfs syscalls for > on the same partition while it is running (even r/o ones might be harmful > if they caused reads of metadata which might be inconsistent). Then when > fsck has finished it calls mount(... MNT_RELOAD...) to sync the metadata. > growfs doesn't do this, and even if it did it is not clear that it does > all the necessary syncing (growfs may change more or different metadata). > However, I think it does most of the necessary things. FYI, I submitted a bug/enhancement request to summarize this.. http://www.freebsd.org/cgi/query-pr.cgi?pr=46110 -Archie P.S. Why does submitting a bug now generate an email response from (and who the heck is) "ThinkHost Support" ?? __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212090448.gB94mO59099523>