From owner-freebsd-current Sun Mar 18 8: 1:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from acampi.inet.it (acampi.inet.it [213.92.4.194]) by hub.freebsd.org (Postfix) with SMTP id A687037B719 for ; Sun, 18 Mar 2001 08:01:20 -0800 (PST) (envelope-from andrea@webcom.it) Received: (qmail 10961 invoked from network); 18 Mar 2001 17:00:14 -0000 Received: from unknown (HELO webcom.it) (212.34.222.47) by acampi.inet.it with SMTP; 18 Mar 2001 17:00:14 -0000 Received: (qmail 10004 invoked by uid 1000); 18 Mar 2001 15:57:50 -0000 Date: Sun, 18 Mar 2001 16:57:49 +0100 From: Andrea Campi To: Thomas Cc: current@freebsd.org Subject: Re: growfs Message-ID: <20010318165749.A725@webcom.it> References: <20010311141337.A510@webcom.it> <20010317110034.62878@Netz-Werker.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010317110034.62878@Netz-Werker.NET>; from tomsoft@Netz-Werker.COM on Sat, Mar 17, 2001 at 11:00:34AM +0100 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This was completely untested by us, and is not guaranteed to work! I think > you were lucky. We move and change blocks on the filesystem, during some > time the filesystem is NOT consitent, so if one of those files is accessed than > you might run into a panic. Sorry? In single user with a readonly / and nothing else? I would have to be EXTREMELY unlucky to get any other access while the fs is inconsistent ;-) Seriously, I get the point (shit happens doesn't it?), but this prompts my next question: isn't this the same as running fsck? Maybe with growfs we have a longer window of inconsistency, but the idea is mostly the same. I think there should be (probably there already is) a way to "reserve" access to the fs, so that no other process can possibly get an inconsistent state. -- Speak softly and carry a cellular phone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message