Date: Mon, 04 Feb 2008 00:40:28 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: gjournal panic 7.0-RC1 Message-ID: <fo5jdd$96g$2@ger.gmane.org> In-Reply-To: <3aaaa3a0802031323obec30f0ubf23dfd01557d287@mail.gmail.com> References: <3aaaa3a0802030751w69ce59a9oeb869e3d87d92616@mail.gmail.com> <fo58j1$7hq$1@ger.gmane.org> <3aaaa3a0802031323obec30f0ubf23dfd01557d287@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Chris wrote: >> AFAIK this means that the journal is too small for your machine - try >> doubling it until there are no more panics. >> >> 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. >> >> >> > > To double it is to do another newfs and start from scratch again or > can I somehow increase the size without losing the data on the drive? If you use an external journal, you can re-create the journal keep the data, if you use an "inline" journal on the same drive as the file system (the default configuration), you need to re-create both the journal and the file system (newfs). > Does a larger journal incease write speeds as I am finding them very > poor around 60% of a sync + soft updates drive. No. An external journal could help you to increase the performance. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHplDsldnAQVacBcgRAiVBAKDjGkq4G+F1QHyeAFuW0+Ky/459gQCdFDks OvTBenUnNw2OvzHEM0+hXX0= =wm6d -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fo5jdd$96g$2>