From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown after Raid crash
Date: Wed, 4 Feb 2009 16:24:27 +0100 [thread overview]
Message-ID: <200902041624.32354@zmi.at> (raw)
In-Reply-To: <20090204122241.GL24173@disturbed>
[-- Attachment #1.1: Type: text/plain, Size: 2293 bytes --]
(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?
I'd like to have a paragraph for normal XFS users, a PC with harddisks,
maybe with onboard RAID1 or 10. So if I could let the paragraph, that
should be OK (as I hope the root dir destroy is a very, very seldom
case).
> > With a RAID controller with battery backed cache, you should turn
> > off barriers, as recommended above. But then you *must* disable the
> > hard disk write cache in order to ensure to keep the filesystem
> > intact after a power failure.
>
> I'd change this to say "*must* disable the individual hard disk
> write caches" to make it clear that it is referencing the disks
> behind the raid controller. I'd also say "The method for doing this
> is different for each RAID controller. Please consult your RAID
> controller documentation to determine how to change these settings."
That sounds good and I'll put it in.
On Mittwoch 04 Februar 2009 Emmanuel Florac wrote:
> I have some controllers at hand, and I had a quick glance :
> - Areca : Allows setting individual cache for passthru disks, needs
> actual testing for drives part of an array.
Areca allows "Disk Write Cache Mode" on/off under "System Controls" ->
"System Config" in the archttpd web interface, plus per Volume write
back cache on/off, but that's not relevant when using battery (and those
who don't - don't care anyway about their data).
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-04 15:25 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 [this message]
2009-02-05 8:37 ` Dave Chinner
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=200902041624.32354@zmi.at \
--to=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 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.