From: Ric Wheeler <rwheeler@redhat.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Julien FERRERO <jferrero06@gmail.com>, xfs@oss.sgi.com
Subject: Re: XFS filesystem corruption
Date: Wed, 06 Mar 2013 18:12:06 -0500 [thread overview]
Message-ID: <5137CD46.6070909@redhat.com> (raw)
In-Reply-To: <20130306232100.6286f640@galadriel.home>
On 03/06/2013 05:21 PM, Emmanuel Florac wrote:
> Le Wed, 6 Mar 2013 17:16:31 +0100 vous écriviez:
>
>> I don't think the H/W RAID is
>> the issue since we have the same corruption with other setup without
>> H/W RAID.
> HW RAID may exacerbate the problem. XFS is absolutely, definitely not
> "brutal power off" safe. All linux systems from this century are
> perfectly able to turn themselves off properly at a single press of the
> power button; the only safe options are educating the users or mounting
> the filesystem read-only.
>
> And yes, the ls garbled output is caracteristic of a filesystem
> corruption.
>
We actually test brutal "Power off" for xfs, ext4 and other file systems. If
your storage is configured properly and you have barriers enabled, they all pass
without corruption.
What hardware raid cards can do is to hide a volatile write cache. Either on the
raid HBA itself or, even worse, on the backend disks behind the card. S-ata
disks tend to default to write cache enabled and need to be checked especially
careful (sas drives tend to be write cache disabled by default).
ric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-06 23:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 15:08 XFS filesystem corruption Julien FERRERO
2013-03-06 15:15 ` Emmanuel Florac
2013-03-06 16:16 ` Julien FERRERO
2013-03-06 16:47 ` Ric Wheeler
2013-03-06 22:21 ` Emmanuel Florac
2013-03-06 23:12 ` Ric Wheeler [this message]
2013-03-07 13:15 ` Julien FERRERO
2013-03-07 13:40 ` Ric Wheeler
2013-03-07 23:22 ` Dave Chinner
2013-03-08 10:16 ` Julien FERRERO
2013-03-12 9:57 ` Martin Steigerwald
2013-03-08 8:39 ` Stan Hoeppner
2013-03-08 10:17 ` Julien FERRERO
2013-03-08 12:20 ` Ric Wheeler
2013-03-08 18:59 ` Stan Hoeppner
2013-03-09 9:11 ` Dave Chinner
2013-03-09 18:51 ` Stan Hoeppner
2013-03-10 22:45 ` Dave Chinner
2013-03-10 23:54 ` Stan Hoeppner
2013-03-11 0:50 ` Dave Chinner
2013-03-11 9:29 ` Stan Hoeppner
2013-03-11 22:45 ` Dave Chinner
2013-03-11 9:25 ` Julien FERRERO
2013-03-12 10:54 ` Emmanuel Florac
2013-03-12 10:42 ` Martin Steigerwald
2013-03-12 22:16 ` Stan Hoeppner
2013-03-07 3:56 ` Stan Hoeppner
2013-03-07 13:04 ` Julien FERRERO
2013-03-07 13:32 ` Stan Hoeppner
2013-03-10 2:50 ` Eric Sandeen
2013-03-10 22:11 ` Dave 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=5137CD46.6070909@redhat.com \
--to=rwheeler@redhat.com \
--cc=eflorac@intellique.com \
--cc=jferrero06@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