Date: Thu, 17 Aug 2006 10:25:29 -0500 From: Eric Anderson <anderson@centtech.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. Message-ID: <44E48A69.9010108@centtech.com> In-Reply-To: <20060817152059.GD78978@garage.freebsd.pl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44E48A69.9010108>