Date: Sun, 12 Oct 2008 16:13:26 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-geom@freebsd.org Subject: Re: Problems with journal? Message-ID: <gct0m9$mcu$1@ger.gmane.org> In-Reply-To: <48F1C760.1080902@zirakzigil.org> References: <48DE439C.4050505@zirakzigil.org> <48F1C760.1080902@zirakzigil.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig944EA1D4A61F55876793181E
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Giulio Ferro wrote:
> Giulio Ferro wrote:
>> I'm experiencing very serious delay issues in 2 production servers.
> [...]
>>
>> I hope any of you can help me look in the right direction, and point
>> me to any further tests to try or tunable
>> to set...
>>
>> Thanks in advance.
>>
>=20
> I didn't receive any answer to this, so I'm guessing ufs journal
> is abandoned or there is no interest in supporting it in production
> environment.
> Anyway I removed it from my servers and reverted to standard UFS,
> so the problems disappeared. I also tried zfs (the only other journale=
d
> filesystem available on freebsd). I didn't experiences the hanging beha=
vior
> I did with journaled ufs, but it's considerably slower than standard uf=
s
> (1/2 slower writes, 1/10 slower reads)...
Both gjournal and ZFS are still "experimental" as far as stability and
performance is concerned (actually, I have the feeling that gjournal
itself is simple enough to be ok but it exposes timing problems with
UFS...), but you might help by giving more information about your problem=
:
* send output from top (with "S" mode) and vmstat ("vmstat 1") when you
experience your slowdown problem
* create a kernel core dump (see
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern=
eldebug.html#KERNELDEBUG-OBTAIN
and
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern=
eldebug-online-ddb.html
, enter "call doadump" on the online debugger prompt) when your problem
starts.
* attach a debugger to the kernel dump, record and send output of "ps",
"show pcpu", "show allpcpu", "show locks", "show alllocks", "show
lockedvnods" and "alltrace."
These are just generic tips, I don't have an idea what might cause your
problems (so some of the information I requested might be useless, but
better to send as much as possible; maybe someone will see something
interesting).
--------------enig944EA1D4A61F55876793181E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjyBgYACgkQldnAQVacBciHwgCdFV2YnrX1SQ7gcYcEenwID4gi
0OUAoJs/Lu/psDFfCkqeBxUDMp3kM7Mx
=16uK
-----END PGP SIGNATURE-----
--------------enig944EA1D4A61F55876793181E--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gct0m9$mcu$1>