From owner-freebsd-current Sat Dec 7 13: 0:16 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 8B6D137B401; Sat, 7 Dec 2002 13:00:14 -0800 (PST) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E39943ED1; Sat, 7 Dec 2002 13:00:13 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc03.attbi.com (sccrmhc03) with ESMTP id <2002120721001200300cvia4e>; Sat, 7 Dec 2002 21:00:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA55669; Sat, 7 Dec 2002 12:57:53 -0800 (PST) Date: Sat, 7 Dec 2002 12:57:51 -0800 (PST) From: Julian Elischer To: Archie Cobbs Cc: Bruce Evans , Kirk McKusick , freebsd-current@FreeBSD.ORG, Thomas-Henning von Kamptz Subject: Re: backgroud fsck is still locking up system (fwd) In-Reply-To: <200212072033.gB7KXddC072338@arch20m.dellroad.org> Message-ID: 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: > > > So in summary my recommendation is to add a big warning to the > > > growfs(1) man page that is should not be run on the root partition, > > > even if you have booted single-user mode and haven't mounted / yet. > > > I.e., to grow a root partition, you must boot from a different partition. > > > > 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. I've seen ufs write back the superblock on unmounting a read-only filesystem (!). it was a few years ago but I wouldn;t be surprised if it was still true.. After you did it on the filesystem. (ran growfs) what did you do next? the safe answer would be to pull the plug. > > In any case, when you're talking about the danger of destroying a > filesystem it probably wouldn't hurt to have a little extra clarity > in the documentation. > > Or better yet, should the kernel prevent raw writes to the / partition? > Guess that would prevent fsck from working though. > > -Archie > > __________________________________________________________________________ > 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