Date: Thu, 17 Aug 2006 17:00:02 +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: <20060817150001.GC78978@garage.freebsd.pl> In-Reply-To: <44E481BE.2080408@centtech.com> References: <20060808195202.GA1564@garage.freebsd.pl> <44E46A68.6080602@centtech.com> <20060817140857.GB78978@garage.freebsd.pl> <44E481BE.2080408@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 17, 2006 at 09:48:30AM -0500, Eric Anderson wrote: > On 08/17/06 09:08, Pawel Jakub Dawidek wrote: > >On Thu, Aug 17, 2006 at 08:08:56AM -0500, Eric Anderson wrote: > >>On 08/08/06 14:52, Pawel Jakub Dawidek wrote: > >>>Hi. > >>>I'm pleased to announce hopefully the final gjournal patches. > >>[..snip..] > >>>To create journaled UFS file system on ad0s1d partition: > >>> # gjournal load > >>> # gjournal label ad0s1d > >>> # newfs -J /dev/ad0s1d.journal > >>> # mount -o noatime,async /dev/ad0s1d.journal /mnt > >>>On reboot 'fsck_ffs -p /dev/ad0s1d.journal' will perform fast check. O= ne > >>>can still run regular check by not giving the -p option. > >>I have a 10TB filesystem I created as above, and recently a crash cause= d it to now complain about the filesystem being dirty. When I do an fsck -= p, here's what I get: > >> > >># fsck -p /dev/label/vol10 > >>/dev/label/vol10: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK > >> > >> > >>/dev/label/vol10: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. > >Do you have log from the boot before you saw this? > >I corrected one bug, but it was only possible to trigger when crash > >happened early in the boot process. Your crash was during or just after > >a boot maybe? >=20 > Yes, I have the logs. What should I send you? I just need 'grep -i journal' from them. > Also, I just tried newfs'ing a new journaled device, and mounting it, the= n a few minutes later, crashing the system (not purposely though), and it t= oo gives the same=20 > results as the other filesystem (same specs, 10Tb, etc). >=20 > The first crash was within about 30 minutes of booting, the second one wa= s about the same time-frame. Maybe there was no writes? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE5IRxForvXbEpPzQRArZ2AJ9MpJE0PmewY65ziM8n9nHFgabFRgCePMD3 qlD1J0dy7fV/q784cKACAiE= =X7eU -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060817150001.GC78978>