From: Dave Chinner <david@fromorbit.com>
To: hank peng <pengxihan@gmail.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs didn't provide redundancy for citical data structure?
Date: Mon, 17 May 2010 09:32:43 +1000 [thread overview]
Message-ID: <20100516233243.GH8120@dastard> (raw)
In-Reply-To: <AANLkTimP06rpMX4BRaRIggMctQ2qR7Cul9yqcJR6Xj3O@mail.gmail.com>
On Sat, May 15, 2010 at 11:57:51PM +0800, hank peng wrote:
> I read this paper: http://pages.cs.wisc.edu/~vshree/xfs.pdf, which
> says xfs didn't provide redundancy for citical data structure, such as
> mirror, parity. I wonder if it is so?
> If it is, is there plan to implement that for XFS developers?
XFS assumes redundancy and protection against bit errors is done in
the block layeri (i.e. RAID of some kind). Changing that assumption
takes a lot of work and involves modifying the disk format, so can't
be done overnight. That being said, work is in progress to make XFS
more robust - see this page for ideas on how we are approaching the
problem:
http://xfs.org/index.php/Reliable_Detection_and_Repair_of_Metadata_Corruption
I'll also point out that the above paper makes some fundamental
mistakes (e.g. XFS does not use "data=ordered" journalling as they
conclude it does from a limited observation). Hence the rest of
their results are somewhat questionable, too, as we can't examine
them closely enough to confirm or deny them....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-05-16 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimP06rpMX4BRaRIggMctQ2qR7Cul9yqcJR6Xj3O@mail.gmail.com>
2010-05-16 2:59 ` xfs didn't provide redundancy for citical data structure? Stan Hoeppner
2010-05-16 23:32 ` Dave Chinner [this message]
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=20100516233243.GH8120@dastard \
--to=david@fromorbit.com \
--cc=pengxihan@gmail.com \
--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