From owner-freebsd-fs@FreeBSD.ORG Thu Aug 17 15:25:06 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36AFC16A4DF; Thu, 17 Aug 2006 15:25:06 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B761943D45; Thu, 17 Aug 2006 15:25:05 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k7HFP5f0094309; Thu, 17 Aug 2006 10:25:05 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44E48A69.9010108@centtech.com> Date: Thu, 17 Aug 2006 10:25:29 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com> <20060817150001.GC78978@garage.freebsd.pl> <44E4851A.6020904@centtech.com> <20060817152059.GD78978@garage.freebsd.pl> In-Reply-To: <20060817152059.GD78978@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1677/Thu Aug 17 08:56:09 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Aug 2006 15:25:06 -0000 On 08/17/06 10:20, Pawel Jakub Dawidek wrote: > On Thu, Aug 17, 2006 at 10:02:50AM -0500, Eric Anderson wrote: >>> Maybe there was no writes? >> There were no writes, absolutely. The only part of the fs that was touched, was the superblock (marking clean/dirty). > > Ok, so this is the bug. When there was only one journal switch, gjournal > will mark device as broken on boot. > This is fixed in perforce already. > > I belive your file system is clean. Do you want to make it > write-accessable again? > Yes, I believe it to be clean too. I can mount it rw, but I'd like to be able to 'convince' it that it is truly clean. Also - did you see my other thread about snapshot deadlock? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------