From: Neil Brown <neilb@suse.de>
To: Don Dupuis <dondster@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Md corruption using RAID10 on linux-2.6.21
Date: Tue, 22 May 2007 10:50:23 +1000 [thread overview]
Message-ID: <18002.15951.765872.809204@notabene.brown> (raw)
In-Reply-To: message from Don Dupuis on Monday May 21
On Monday May 21, dondster@gmail.com wrote:
> On 5/16/07, Don Dupuis <dondster@gmail.com> wrote:
> >
> > I am still trying to get where I had the low recover rate with the
> > bitmap turned on. I will get back with you
> > Don
> >
> Any new updates Neil?
> Any new things to try to get you additional info?
> THanks
>
> Don
You said "I will get back with you" and I was waiting for that... I
hoped that your further testing might reveal some details that would
shine a light on the situation.
One question: Your description seems to say that you get corruption
after the resync has finished. Is the corruption there before the
resync starts?
I guess what I would like it:
Start with fully active array. Check for corruption.
Remove one drive. Check for corruptions.
Turn off system. Turn it on again, array assembles with one
missing device. Check for corruption.
Add device, resync starts. Check for corruption.
Wait for resync to finish. Check for corruption.
NeilBrown
next prev parent reply other threads:[~2007-05-22 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 18:38 Md corruption using RAID10 on linux-2.6.21 Don Dupuis
2007-05-17 1:54 ` Neil Brown
2007-05-17 2:57 ` Don Dupuis
2007-05-17 2:58 ` Don Dupuis
2007-05-17 3:50 ` Don Dupuis
2007-05-21 19:32 ` Don Dupuis
2007-05-22 0:50 ` Neil Brown [this message]
2007-05-22 2:47 ` Don Dupuis
2007-05-22 3:59 ` Neil Brown
2007-05-31 1:52 ` Don Dupuis
2007-05-31 5:16 ` Neil Brown
2007-06-01 15:58 ` Don Dupuis
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=18002.15951.765872.809204@notabene.brown \
--to=neilb@suse.de \
--cc=dondster@gmail.com \
--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).