Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Aug 2008 16:51:49 +0200
From:      Ivan Voras <ivoras@freebsd.org>
To:        freebsd-questions@freebsd.org
Cc:        freebsd-geom@freebsd.org
Subject:   Re: gjournal & fsck
Message-ID:  <g96e22$1l7$1@ger.gmane.org>
In-Reply-To: <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com>
References:  <2b5f066d0808280705y3454c188v768efe46b388864b@mail.gmail.com>	<g96d2h$sp2$1@ger.gmane.org> <2b5f066d0808280743g69c32d1rd30aee0ca276125@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig69D26AE0D395E8B4B85C7A70
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Brian McCann wrote:

> Yes...I apologize...I did that when I built the file system with
> "newfs -J".  Here's the tunefs -p output for one of the file systems:
>=20
> # tunefs -p /dev/da2.journal
> tunefs: ACLs: (-a)                                         disabled
> tunefs: MAC multilabel: (-l)                               disabled
> tunefs: soft updates: (-n)                                 disabled
> tunefs: gjournal: (-J)                                     enabled
> tunefs: maximum blocks per file in a cylinder group: (-e)  2048
> tunefs: average file size: (-f)                            16384
> tunefs: average number of files in a directory: (-s)       64
> tunefs: minimum percentage of free space: (-m)             8%
> tunefs: optimization preference: (-o)                      time
> tunefs: volume label: (-L)
>=20
> I'm concerned about this because the ones I've had problems with
> recently are 1.1TB arrays...I've got 2 8.6TB arrays that are journaled
> as well...and if I ever have to fsck them...that could take 1/2 the
> day...
>=20
> Any other thoughts?

Ok.

There was one person that complained about fsck on gjournal but not in
the same context - he created the journal for gjournal on an existing
file system and so destroyed a part of the data. I don't think this is
related to your case.

Does gjournal complain about your drive, for example that it doesn't
support BIOFLUSH?

Also, did fsck actually do something when it was started (did it find
anything corrupted)?


--------------enig69D26AE0D395E8B4B85C7A70
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFItruFldnAQVacBcgRAjDiAKD6XHUCyxxJdWVrd7EzluEEpWrYjQCfdvEk
OjSgJSp7uossW4PCa3pAcPU=
=dXql
-----END PGP SIGNATURE-----

--------------enig69D26AE0D395E8B4B85C7A70--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g96e22$1l7$1>