From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: No syncing after crash. Is this a software raid bug?
Date: Sat, 4 Mar 2006 14:38:43 +0100 [thread overview]
Message-ID: <duc593$uan$1@sea.gmane.org> (raw)
In-Reply-To: 20060304131609.GA4064@erwin.lan
Kasper Dupont <10616252720827252562@expires.05.sep.2006.kasperd.net> wrote:
> And by that you mean that raid5 and raid6 must copy the page
> contents before writing it to disk?
They must not :) But if they don't, they risk inconsistent parity
information to be calculated.
However, since "inconsistent parity information in raid[456] is equal
to "different mirrors" in raid1, there is no real difference. So I
doubt they will copy :)
regards
Mario
--
<jv> Oh well, config
<jv> one actually wonders what force in the universe is holding it
<jv> and makes it working
<Beeth> chances and accidents :)
next prev parent reply other threads:[~2006-03-04 13:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 12:44 No syncing after crash. Is this a software raid bug? Kasper Dupont
2006-03-01 13:58 ` Luca Berra
2006-03-01 16:24 ` Mike Hardy
2006-03-01 21:56 ` Kasper Dupont
2006-03-02 13:48 ` Mario 'BitKoenig' Holbe
2006-03-03 13:39 ` Heinz Mauelshagen
2006-03-03 14:30 ` Mario 'BitKoenig' Holbe
2006-03-03 22:26 ` Heinz Mauelshagen
2006-03-03 23:01 ` Mario 'BitKoenig' Holbe
2006-03-04 9:01 ` Heinz Mauelshagen
2006-03-04 10:10 ` Mario 'BitKoenig' Holbe
2006-03-03 7:30 ` Kasper Dupont
2006-03-03 12:03 ` Mario 'BitKoenig' Holbe
2006-03-03 12:38 ` Mario 'BitKoenig' Holbe
2006-03-03 14:48 ` Kasper Dupont
2006-03-03 15:10 ` Mario 'BitKoenig' Holbe
2006-03-04 13:16 ` Kasper Dupont
2006-03-04 13:38 ` Mario 'BitKoenig' Holbe [this message]
2006-03-04 19:50 ` Kasper Dupont
2006-03-07 10:47 ` Heinz Mauelshagen
2006-03-07 11:18 ` Kasper Dupont
2006-03-07 12:12 ` Heinz Mauelshagen
2006-03-10 7:43 ` Heinz Mauelshagen
2006-03-10 7:49 ` Kasper Dupont
2006-03-16 7:24 ` Kasper Dupont
2006-03-16 14:04 ` Heinz Mauelshagen
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='duc593$uan$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).