Date: Fri, 18 Apr 2008 21:18:54 -0700 (PDT) From: Unga <unga888@yahoo.com> To: freebsd-questions@freebsd.org Cc: Ivan Voras <ivoras@freebsd.org> Subject: Re: UFS2 Journaling implementation detail Message-ID: <759748.83603.qm@web57009.mail.re3.yahoo.com> In-Reply-To: <9bbcef730804180840y77adff73x7ad0cf90c82633a9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Ivan Voras <ivoras@freebsd.org> wrote:
> > Does it log anywhere if the journal size is too
> small for the system load?
>
> Yes, you'll get a system panic in this case. Yes,
> it's a bad solution, complain to Pawel :)
>
So the gjournal can corrupt the file system as well as
can fix it :)
I think this is a serious concern for desktop users
rather than servers. For those who do multi-channel
audio encoding, HD/35mm-full-frame video encoding,
batch conversion of photos, etc. may hit the default
1GB journal size and end up in system panic.
I think because of this gjournal implementation issue,
gjournal requires a huge journal.
Just for a thought, in my opinion, gjournal should not
use the entire journal for logging. May be split it
two. Ie. From size S given, use two journals. When one
journal is full, point the new changes to go to the
second journal, and flush the first journal and so on.
If the gjournal has to flush too often, then log it in
the system log that journal is too small.
Ivan, thanks again for detail.
Kind regards
Unga
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?759748.83603.qm>