public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RAID-5 design bug (or misfeature)
Date: Tue, 31 May 2005 10:05:33 +0200	[thread overview]
Message-ID: <429C1ACD.8070600@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.58.0505301759550.6859@artax.karlin.mff.cuni.cz>

Mikulas Patocka wrote:

>
>I think that's another problem --- when RAID-5 is operating in degraded
>mode, the machine must not crash or volume will be damaged (sectors
>that were not written may be damaged this way). Did anybody develop some
>method to care about this (i.e. something like journaling on raid)? What
>do hardware RAID controllers do in this situation?
>  
>
Hot spares can keep the degraded time to a minimum.  If you want to
keep the risk to a minimum, unmount the raid fs until it is
resynchronized.  If you need more safety, there is options like raid-6
or mirrors of the entire raid-5 set.

Some hw controllers have a battery-backed cache.  Even a power loss
won't ruin the raid - the io will simply sit in that cache until the
disks become available again.  The io operation that was in effect when
power was lost can then be retried. Not that this saves you from everything,
the fs could be inconsistent anyway due to the os being killed in the
middle of its updates. A journalled fs can help with that though.

Helge Hafting

  reply	other threads:[~2005-05-31  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-29 22:53 RAID-5 design bug (or misfeature) Mikulas Patocka
2005-05-29 23:01 ` Wakko Warner
2005-05-29 23:58 ` Bernd Eckenfels
2005-05-30  2:47   ` Mikulas Patocka
2005-05-30  3:00     ` Bernd Eckenfels
2005-05-30 11:55     ` Alan Cox
2005-05-30 13:23       ` Stephen Frost
2005-05-30 16:09       ` Mikulas Patocka
2005-05-31  8:05         ` Helge Hafting [this message]
2005-05-31 21:39         ` Pavel Machek
2005-06-01  1:43           ` Mikulas Patocka
2005-06-01 18:18       ` Bill Davidsen

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=429C1ACD.8070600@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    /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