On Thu, Aug 28, 2008 at 10:34 AM, Ivan Voras <[EMAIL PROTECTED]> 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 >
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: # 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) 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... Any other thoughts? Thanks for the help so far Ivan! --Brian _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"