All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Mike Ashton <mike@fysh.org>
Cc: xfs@oss.sgi.com
Subject: Re: fsck.xfs proposed improvements
Date: Wed, 22 Apr 2009 23:45:11 +0200	[thread overview]
Message-ID: <87ws9cnz14.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090422094527.GA16600@fysh.org> (Mike Ashton's message of "Wed, 22 Apr 2009 10:45:27 +0100")

Mike Ashton <mike@fysh.org> writes:

> With badly behaved hardware,
> which seem prevalent, or any bugs which do get into xfs we could
> actually end up with xfs being less fault tolerant and less reliable
> in general use than other filesystems, which would be a bit of a
> shame.

Most Linux file systems are not very fault tolerant in this sense;
e.g. on ext3 you have have to press return and accept lots of scary
messages to get through fsck.

-Andi
 

-- 
ak@linux.intel.com -- Speaking for myself only.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-04-22 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1240318659.128675.xfs@oss.sgi.com>
2009-04-21 14:23 ` fsck.xfs proposed improvements Mike Ashton
2009-04-21 22:09   ` Russell Cattelan
2009-04-22  9:45     ` Mike Ashton
2009-04-22 21:45       ` Andi Kleen [this message]
2009-04-23  8:49         ` Mike Ashton
2009-04-23 12:45           ` Eric Sandeen
     [not found]             ` <20090423141432.GC16600@fysh.org>
2009-04-23 14:35               ` Mike Ashton
2009-04-23 16:19                 ` Russell Cattelan
2009-04-24  9:21                   ` Mike Ashton

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=87ws9cnz14.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=mike@fysh.org \
    --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 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.