From: Kasper Dupont <61795653253942064414@expires.08.sep.2006.kasperd.net>
To: Heinz Mauelshagen <mauelshagen@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: No syncing after crash. Is this a software raid bug?
Date: Tue, 7 Mar 2006 12:18:35 +0100 [thread overview]
Message-ID: <20060307111835.GA15648@hactar.lan> (raw)
In-Reply-To: <20060307104704.GD2976@redhat.com>
On 07/03/06 11.47, Heinz Mauelshagen wrote:
> On Sat, Mar 04, 2006 at 02:16:11PM +0100, Kasper Dupont wrote:
> > > If it relies on static page content during updates of its mirrors, it
> > > need to take a private copy of the page(s).
> >
> > And by that you mean that raid5 and raid6 must copy the page
> > contents before writing it to disk?
>
> Yes.
> They need to do it anayway in order to calculate parity blocks.
OK, I'll do some testing with raid5 then. I want to know if it
behaves differently from raid1 in this respect.
--
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my new email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,6,_+2,_+7,_+6);
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-03-07 11:18 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
2006-03-04 19:50 ` Kasper Dupont
2006-03-07 10:47 ` Heinz Mauelshagen
2006-03-07 11:18 ` Kasper Dupont [this message]
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=20060307111835.GA15648@hactar.lan \
--to=61795653253942064414@expires.08.sep.2006.kasperd.net \
--cc=linux-raid@vger.kernel.org \
--cc=mauelshagen@redhat.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;
as well as URLs for NNTP newsgroup(s).