Date: Fri, 1 Sep 2006 20:56:37 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Kevin Kramer <kramer@centtech.com> Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions Message-ID: <20060901185637.GA6759@garage.freebsd.pl> In-Reply-To: <44F84EB9.6000006@centtech.com> References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> <20060901145939.GC1819@garage.freebsd.pl> <44F84EB9.6000006@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--17pEHd4RhPHOinZp Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 01, 2006 at 10:16:09AM -0500, Kevin Kramer wrote: > I've already redone the whole thing. here are the steps i took >=20 > umount /scr09 > umount /scr10 > gjournal stop da2.journal > gjournal stop da4.journal >=20 > ** had not done this on the first attempt > newfs /dev/da1 > newfs /dev/da3 This is not needed. > gjournal label -v /dev/da2 /dev/da1 > gjournal label -v /dev/da4 /dev/da3 >=20 > newfs -J -L scr09 /dev/da2.journal > newfs -J -L scr10 /dev/da4.journal >=20 > mount /scr09 > mount /scr10 Don't know how your /etc/fstab looks like, but you definiately should use 'async' mount option, which is safe to use with gjournaled file systems. > it is looking much better so far. before, i was getting this in the debug= (only on /scr10) and my mountd process was always the top process >=20 > Sep 1 00:00:11 donkey kernel: fsync: giving up on dirty > Sep 1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR > Sep 1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 mou= ntedher > e 0xc9ebfb00 > Sep 1 00:00:11 donkey kernel: flags () > Sep 1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933 > Sep 1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread = 0xc9bd4 > 180 (pid 38) > Sep 1 00:00:11 donkey kernel: dev ufs/scr10 > Sep 1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system /= scr10 ( > error=3D35). It happens sometimes under load, haven't investigated yet what exactly is happening, but you can ignore it for now, it's harmless, it just means journal switch will be done a bit later. BTW. 8GB for journals is much. You should not need more than 2GB probably. Of course it will work with 8GB just fine. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE+IJlForvXbEpPzQRAqSWAJ92yOYLIlQbJEGthTRpLhtDix+/WwCcCLW/ qzcp6QskinL3EkkXK8BUwFw= =91Hb -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060901185637.GA6759>