public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown after Raid crash
Date: Thu, 5 Feb 2009 19:37:00 +1100	[thread overview]
Message-ID: <20090205083700.GO24173@disturbed> (raw)
In-Reply-To: <200902041624.32354@zmi.at>

On Wed, Feb 04, 2009 at 04:24:27PM +0100, Michael Monnerie wrote:
> (compressing 2 answers here)
> 
> On Mittwoch 04 Februar 2009 Dave Chinner wrote:
> > > With a single hard disk and barriers turned on (on=default), a
> > > powerfail "only" looses data in the cache but at least does not
> > > destroy the filesystem.
> >
> > I'd drop this paragraph - powerfail can destroy filesystems even on
> > a single disk (e.g. root directory gets corrupted).
> 
> Isn't that what barriers are for? If I understand correctly, barriers 
> help against destroying the filesys, except root dir? But that should 
> "easily" be fixable with xfs_repair or so?

See, I didn't understand what you were trying to say. ;)

What I missed was the "barriers turned on" - I was referring
(context not quoted) to the fact that RAID5 is not unіque in it's
ability to trash the filesystem on powerfail. You are right,
barriers on a single disk should prevent filesystem corruption
and will prevent loss of synchronously written data. only
asynchronously written data will get lost (just like all the
stuff sitting in RAM).

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2009-02-05  8:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 21:53 xfs_force_shutdown after Raid crash Steffen Knauf
2009-01-31 10:57 ` Christoph Hellwig
2009-02-03  1:22   ` Michael Monnerie
2009-02-03  3:13     ` Eric Sandeen
2009-02-03  9:22       ` Michael Monnerie
2009-02-03  9:32         ` Christoph Hellwig
2009-02-03 10:40           ` Michael Monnerie
2009-02-03 15:49             ` Christoph Hellwig
2009-02-04  8:52               ` Michael Monnerie
2009-02-04 10:27                 ` Michael Monnerie
2009-02-04 12:26                   ` Dave Chinner
2009-02-04 15:03                     ` Michael Monnerie
2009-02-13 10:12                       ` Michael Monnerie
2009-02-04 12:22                 ` Dave Chinner
2009-02-04 12:45                   ` Emmanuel Florac
2009-02-04 14:01                     ` KELEMEN Peter
2009-02-04 15:15                       ` Emmanuel Florac
2009-02-04 15:25                         ` Michael Monnerie
2009-02-04 15:41                         ` KELEMEN Peter
2009-02-04 16:01                           ` Michael Monnerie
2009-02-04 16:23                           ` Emmanuel Florac
2009-02-04 15:24                   ` Michael Monnerie
2009-02-05  8:37                     ` Dave Chinner [this message]
2009-02-04 15:33                   ` Ralf Liebenow
2009-02-04 16:18                     ` Michael Monnerie
2009-02-05  8:22                       ` Michael Monnerie
2009-02-05 12:05                         ` Emmanuel Florac
2009-02-06 15:57   ` Steffen Knauf

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=20090205083700.GO24173@disturbed \
    --to=david@fromorbit.com \
    --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