From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: XFS and XEN
Date: Tue, 24 Feb 2009 11:38:23 -0500 [thread overview]
Message-ID: <20090224163823.GA19811@infradead.org> (raw)
In-Reply-To: <200902241604.29566@zmi.at>
On Tue, Feb 24, 2009 at 04:04:24PM +0100, Michael Monnerie wrote:
> if you don't have highly reliable hardware, with redundant channels and
> battery backed caches, etc. stay away from XFS.
>
> it's a pity, but XFS is only as reliable as the hardware you give it.
> in other words: you can be really sure that a software issue won't trash
> your XFS filesystem; but also that a hardware failure definitely will.
>
> ext3, OTOH, might not have such an impressive record of correctness; but
> it's designed with redundancy in mind. almost all vital structures are
> either replicated or reconstructable from other hints. that makes fsck
> slow but effective, and in most cases, the journal analysis done when
> remounting after an unclean shutdown is enough to put it back on track.
>
> i sure wish i could use XFS in more circumstances, but the needed
> hardware is prohibitive.
It's the usual BS. The difference is just that you actually see the
corruption on XFS while it's pretty silent on extN. If your Hardware
(or Hypervisor) is not reliable you _will_ lose data. Either silently
or with a spectacular blowup if the filesystem actually has consistency
checking (which XFS has a lot).
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-24 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 8:59 XFS and XEN Michael Monnerie
2009-02-17 9:11 ` Christoph Hellwig
2009-02-17 14:00 ` Michael Monnerie
2009-02-19 19:35 ` Christoph Hellwig
2009-02-21 9:03 ` Michael Monnerie
2009-02-24 15:04 ` Michael Monnerie
2009-02-24 16:38 ` Christoph Hellwig [this message]
2009-02-25 6:40 ` Michael Monnerie
2009-03-05 6:44 ` Michael Monnerie
2009-03-03 20:56 ` Michael Monnerie
2009-03-04 2:42 ` Michael Monnerie
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=20090224163823.GA19811@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox