Date: Thu, 17 Aug 2006 17:20:59 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-fs@FreeBSD.org, freebsd-geom@FreeBSD.org Subject: Re: GJournal (hopefully) final patches. Message-ID: <20060817152059.GD78978@garage.freebsd.pl> In-Reply-To: <44E4851A.6020904@centtech.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--5p8PegU4iirBW1oA Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 10:02:50AM -0500, Eric Anderson wrote: > >Maybe there was no writes? >=20 > There were no writes, absolutely. The only part of the fs that was touch= ed, 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? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --5p8PegU4iirBW1oA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE5IlbForvXbEpPzQRAh1WAKDlLyvW6af5WZshCV2oM3LvGC0FnACgjBI0 jzEmu602KDd1KeMSol4vk7g= =+DPp -----END PGP SIGNATURE----- --5p8PegU4iirBW1oA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060817152059.GD78978>