public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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 09:52:45 +0100	[thread overview]
Message-ID: <200902040952.45440@zmi.at> (raw)
In-Reply-To: <20090203154907.GA21278@infradead.org>

On Dienstag 03 Februar 2009 Christoph Hellwig wrote:
> Yeah, that sounds correct.  Do you volunteer for the FAQ entry?
>  xfs.org is a wiki so you could add it.  I'm happy to proof-read it
> if you want.

I don't know if it's good and correct, I just put this in the wiki, and 
additionally changed 2 sections, please check the wiki log if it's 
correct:

== Q. What about the hard disk write cache? ==

The problem with hard disk write caches is that their contents are lost 
in case of a power outage. With hard disk cache sizes of currently up to 
32MB that can be a lot of valuable information.

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.

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.

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

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

  reply	other threads:[~2009-02-04  8:53 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 [this message]
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
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=200902040952.45440@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox