public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Grozdan Nikolov <microchip@chello.be>
To: xfs@oss.sgi.com
Subject: adding more redundancy in XFS?
Date: Thu, 21 Dec 2006 04:42:32 +0100	[thread overview]
Message-ID: <200612210442.33706.microchip@chello.be> (raw)

Hi,

I have a simple question regarding XFS. A while back ago I read a research 
paper about the IRON (Internal Robustness) of file systems that tests and 
compares various Linux file systems on how they handle data-integrity in case 
of a unclean unmount or power failure or even a disk failure. Though I'm not 
a file system guru like you guys I learned that XFS does a fairly good job 
but fails bad in specific areas, like, and I quote from the paper: "when an 
ordered data block write fails, XFS continues to log the failed transaction 
to the journal resulting in data corruption"

The paper can be downloaded here: http://www.cs.wisc.edu/adsl/Publications/
(just click on the IRON file systems link for a PDF)

My question is, is it possible to add to XFS more sanity checking (maybe even 
CRC checks?) on things like inodes, bitmaps, indirect pointers, etc to 
further improve the integrity of XFS?

Thanks, GN
-- 
Windows: a 64-bit service pack to a 32-bit extension and GUI shell to a 16-bit 
patch to an 8-bit operating system originally coded for a 4-bit 
microprocessor and sold by a 2-bit company than can't stand 1-bit of 
competition

             reply	other threads:[~2006-12-21  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  3:42 Grozdan Nikolov [this message]
2006-12-21  6:36 ` adding more redundancy in XFS? David Chinner

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=200612210442.33706.microchip@chello.be \
    --to=microchip@chello.be \
    --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