From: NeilBrown <neilb@suse.de>
To: Manibalan P <pmanibalan@amiindia.co.in>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
Date: Thu, 13 Mar 2014 17:19:02 +1100 [thread overview]
Message-ID: <20140313171902.2a767027@notabene.brown> (raw)
In-Reply-To: <13688C12F44C7C428726663F950CA253094ADEC6@venus.in.megatrends.com>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On Wed, 12 Mar 2014 13:09:28 +0530 "Manibalan P" <pmanibalan@amiindia.co.in>
wrote:
> >
> >Was the array fully synced before you started the test?
>
> Yes , IO is started, only after the re-sync is completed.
> And to add more info,
> I am facing this mis-compare only with high resync speed
> (30M to 100M), I ran the same test with resync speed min -10M and max -
> 30M, without any issue. So the issue has relationship with
> sync_speed_max / min.
So presumably it is an interaction between recovery and IO. Maybe if we
write to a stripe that is being recoverred, or recover a stripe that is being
written to, then something gets confused.
I'll have a look to see what I can find.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-03-13 6:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 7:39 raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed Manibalan P
2014-03-13 6:19 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-24 13:15 Manibalan P
2014-04-11 12:11 Manibalan P
2014-04-23 7:07 ` NeilBrown
2014-04-23 17:02 ` Dan Williams
2014-05-05 7:21 ` NeilBrown
2014-05-16 18:11 ` Dan Williams
2014-05-20 0:22 ` Dan Williams
2014-05-22 11:47 ` Manibalan P
2014-05-22 11:52 ` Manibalan P
2014-04-23 9:19 ` Pasi Kärkkäinen
2014-04-23 9:25 ` Manibalan P
2014-04-23 9:30 ` Pasi Kärkkäinen
2014-04-23 9:33 ` Manibalan P
2014-04-23 9:45 ` Pasi Kärkkäinen
2014-04-23 9:59 ` Manibalan P
2014-04-23 10:03 ` Pasi Kärkkäinen
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=20140313171902.2a767027@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=pmanibalan@amiindia.co.in \
/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).