From owner-freebsd-current Sat Dec 7 13:54: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D62E37B401; Sat, 7 Dec 2002 13:54:06 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 329BD43EC2; Sat, 7 Dec 2002 13:54:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA19993; Sun, 8 Dec 2002 08:53:47 +1100 Date: Sun, 8 Dec 2002 08:54:03 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Archie Cobbs Cc: Kirk McKusick , Julian Elischer , , Thomas-Henning von Kamptz Subject: Re: backgroud fsck is still locking up system (fwd) In-Reply-To: <200212072033.gB7KXddC072338@arch20m.dellroad.org> Message-ID: <20021208083912.G14505-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 7 Dec 2002, Archie Cobbs wrote: > 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message