Date: Thu, 28 Aug 2008 21:05:51 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Brian McCann <bjmccann@gmail.com> Cc: freebsd-geom@freebsd.org, Ivan Voras <ivoras@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: gjournal & fsck Message-ID: <20080828190550.GC2292@garage.freebsd.pl> 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
--TiqCXmo5T1hvSQQg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 28, 2008 at 10:43:58AM -0400, Brian McCann wrote: > On Thu, Aug 28, 2008 at 10:34 AM, Ivan Voras <ivoras@freebsd.org> wrote: > > Brian McCann wrote: > >> Hi all. I'm having some problems with several servers I've built > >> recently (7.0-RELEASE) that are using gjournal. I had two reboot a > >> few days ago (un-related to FreeBSD problems I think)...but when they > >> came back up, the file systems wouldn't mount since they were not > >> clean. Now, I understand that UFS knows nothing about the fact that > >> it's journaled, and the journaling knows nothing about UFS...but it's > > > > Actually UFS needs to know about gjournal for just this purpose. There's > > a special option to newfs that tells the file system to be aware of > > gjournal and it should request fscks. > > > >> my understanding that by using gjournal, you should really never need > >> to fsck a file system. However, the only way to get them to mount is > >> by doing the fsck. Is there something else I should be doing instead > >> of fsck? > > > > man 8 tunefs > > >=20 >=20 > 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? Everything looks good. Do you have 'fsck_y_enable' in your rc.conf by any chance? gjournal mode in fsck is only used for -p option, AFAIR. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --TiqCXmo5T1hvSQQg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFItvcOForvXbEpPzQRAq2dAJ9rDDlK+/21oskAZG/FFZ0W89f01ACdFpTt pB039ICtp4uzBL+RtViHSBs= =dWBq -----END PGP SIGNATURE----- --TiqCXmo5T1hvSQQg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080828190550.GC2292>