linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kasper Dupont <40993640693243247796@expires.17.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: Thu, 16 Mar 2006 08:24:52 +0100	[thread overview]
Message-ID: <20060316072450.GA28095@hactar.lan> (raw)
In-Reply-To: <20060310074954.GA23424@hactar.lan>

On 10/03/06 08.49, Kasper Dupont wrote:
> On 10/03/06 08.43, Heinz Mauelshagen wrote:
> > On Tue, Mar 07, 2006 at 12:18:35PM +0100, Kasper Dupont wrote:
> > > 
> > > OK, I'll do some testing with raid5 then. I want to know if it
> > > behaves differently from raid1 in this respect.
> > 
> > Have you got results yet ?
> 
> No, not yet. I'll tell you as soon as I have some.

OK now I have some results. I could not reproduce the symptoms
with raid5. As long as this only shows up with raid1, there is
not much reason to worry.

-- 
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

  reply	other threads:[~2006-03-16  7:24 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
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 [this message]
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=20060316072450.GA28095@hactar.lan \
    --to=40993640693243247796@expires.17.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).