From owner-freebsd-geom@FreeBSD.ORG Fri Nov 3 20:35:04 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7852916A403 for ; Fri, 3 Nov 2006 20:35:04 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id D710D43D6D for ; Fri, 3 Nov 2006 20:35:03 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 66964 invoked by uid 2001); 3 Nov 2006 20:35:02 -0000 Date: Fri, 3 Nov 2006 14:35:02 -0600 From: "Rick C. Petty" To: VANHULLEBUS Yvan Message-ID: <20061103203502.GA66465@keira.kiwi-computer.com> References: <20061102143915.GA26008@zen.inc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061102143915.GA26008@zen.inc> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: FSCKing a RO partition X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Nov 2006 20:35:04 -0000 On Thu, Nov 02, 2006 at 03:39:15PM +0100, VANHULLEBUS Yvan wrote: > > (problem reported first to FreeBSD-hackers, where people told me > "GEOM"....). > > [background] > When the system starts up, root partition is already monted RO, and > fsck works, without any problems, without any warning. As explained on -hackers, this is a bug, introduced at the same time as UFS2, soft updates, background fsck, and GEOM.. that is: 5.x. I hope someone here in -geom can look into it. Maybe filing a PR might help? > But under FreeBSD6 (and I guess 5, but I don't have a running FreeBSD5 > host), fsck says "NO WRITE ACCESS", then starts its stuff (but I fear > what will happen if it detect problems on the filesystem....). It won't be able to fix the problems, because writing has been disabled. This is definately a regression. I started looking into it, but never had the time to produce a patch. -- Rick C. Petty