From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] JFS or XFS
Date: Thu Jan 15 18:33:02 2004 [thread overview]
Message-ID: <1074209572.2152.74.camel@localhost.localdomain> (raw)
In-Reply-To: <20040116002242.47690445@souldaemon>
On Thu, 2004-01-15 at 17:22, neuron wrote:
> reiserfs, guaranteed personally. Especially on a mail server.
> I've used jfs, I crashed it twice on purpose (network swap, then
> disable network card), both times jfs failed to boot. (this is
> because it trusts it's own journal, which a lot of people love about
> it, both times for me it was wrong..)
>
> Personally I haven't had any problems with XFS though, but I haven't
> used it that much.
>
As a note, any journaling FS that uses metadata for updates will have
issues with server AbEnds where there is data in-flux. The
meta-log(journal) will be in some state of flux and depending on the
timing of the AbEnd, then you can be in trouble. The recent XFS code
finally fixes a lot of issues about this with a meta journal update
daemon and set of sysctls that are configurable. Also, another way to
ensure your journal is safe, both with JFS, XFS, ext3 in full logging
mode, is to put your journal on a separate device that may not be
affected by the AbEnd. I can reveal more, but am short on time. I would
personally ask each list of the FS your interested in after you've read
about each.
It should be noted as well that each journaling FS has it's own issues
which are application dependent. i.e. works better in some cases than
others based on usage patterns, file types, etc.
--
Austin Gonyou <austin@coremetrics.com>
Coremetrics, Inc.
next prev parent reply other threads:[~2004-01-15 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 18:19 [linux-lvm] JFS or XFS Rajesh Saxena
2004-01-15 18:24 ` neuron
2004-01-15 18:33 ` Austin Gonyou [this message]
2004-01-15 18:46 ` Greg Freemyer
2004-01-15 19:02 ` Spam
2004-01-20 16:15 ` Steven Lembark
2004-01-15 22:38 ` Austin Gonyou
2004-01-15 19:30 ` Rajesh Saxena
2004-01-16 8:57 ` Heinz Mauelshagen
2004-01-16 17:55 ` Rajesh Saxena
2004-01-16 19:43 ` Alasdair G Kergon
2004-01-16 19:48 ` Dan Sully
2004-01-16 20:06 ` Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074209572.2152.74.camel@localhost.localdomain \
--to=austin@coremetrics.com \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.