From: bas on
I have a system with a 516G gjournal volume mounted as
/dev/stripe/st0g.journal on /home (ufs, asynchronous, local, gjournal)
The system crashed (because of a faulty external usb device). In
single user mode, I ran fsck on the non-gjournal volumes and then
tried to mount the gjournaled volume, which resulted in
WARNING: R/W mount of /home denied. Filesystem is not clean - run
fsck
Which I did. But I thought you could avoid fsck on a large volume if
it was gjournaled. What am I missing?

From: Lowell Gilbert on
bas <babak.ashrafi(a)gmail.com> writes:

> I have a system with a 516G gjournal volume mounted as
> /dev/stripe/st0g.journal on /home (ufs, asynchronous, local, gjournal)
> The system crashed (because of a faulty external usb device). In
> single user mode, I ran fsck on the non-gjournal volumes and then
> tried to mount the gjournaled volume, which resulted in
> WARNING: R/W mount of /home denied. Filesystem is not clean - run
> fsck
> Which I did. But I thought you could avoid fsck on a large volume if
> it was gjournaled. What am I missing?

You can't avoid fsck with gjournal. But it should be very quick.
--
Lowell Gilbert, embedded/networking software engineer
http://be-well.ilk.org/~lowell/
From: bas on
On Jul 21, 1:56 pm, Lowell Gilbert <lguse...(a)be-well.ilk.org> wrote:

> You can't avoid fsck with gjournal.  But it should be very quick.
> --
> Lowell Gilbert, embedded/networking software engineer
>          http://be-well.ilk.org/~lowell/

I see, thanks. Yes, it is quick.