Date: Sun, 03 Feb 2008 22:23:44 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: gjournal panic 7.0-RC1 Message-ID: <fo5bd1$h5r$1@ger.gmane.org> In-Reply-To: <20080203205825.GA62536@in-addr.com> References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> <fo58j1$7hq$1@ger.gmane.org> <20080203205825.GA62536@in-addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Gary Palmer wrote: > On Sun, Feb 03, 2008 at 09:35:44PM +0100, Ivan Voras wrote: >> If so, this is the same class of errors as ZFS (some would call it >> "tuning errors"), only this time the space reserved for the on-disk >> journal is too small, and the fast drives fill it up before data can be >> transfered from the journal to the data area. > > Is there something stopping gjournal from temporarily blocking writes > to the journal to allow it to flush the journaled data to the provider? I've done something like that in the past, but I don't know if Pawel's gjournal has this implemented. I feel that a good solution could be to somehow pause the file system at the VFS layer not to generate requests that would result in IO writes - this could (in theory...) help with ZFS. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHpjDgldnAQVacBcgRAnpuAKCBp41nE55TNHPQ1TNK47+eiWKbkACg6aKf +nGW6jqRPWsxEF+usvN2vnc= =kM2d -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fo5bd1$h5r$1>