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: Tue, 3 Feb 2009 10:22:38 +0100	[thread overview]
Message-ID: <200902031022.38583@zmi.at> (raw)
In-Reply-To: <4987B673.8030406@sandeen.net>

On Dienstag 03 Februar 2009 Eric Sandeen wrote:
> you'd need to read the docs for your controller, to find out how to
> tell if it has a writeback cache enabled, and whether it is
> batter-backed or not.

Sorry I didn't write that. Yes it's writeback (can be switched off) and 
it's battery backed. Is there no danger then? Because in the mail from 
Chris, he wrote he got problems because there was "with a write back 
cache enabled on the controller / disks but without barriers". And I 
thought the (not supported/used) barriers could be a problem.

I've re-read the FAQ now. It says it's recommended to turn off barrier 
writes if you have battery-backed writeback, and I guess I'll do that. 
So I misunderstood Chris.
But what about the hard disk cache - should that be disabled? I think in 
case of a power failure, they just loose their cache contents, right? So 
the battery-backed controller cache only helps himself, the disks will 
just throw away up to the 32MB cache they have?

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-03  9:23 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 [this message]
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
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=200902031022.38583@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