linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: linux-raid@vger.kernel.org
Subject: resync'ing - what is going on
Date: Thu, 10 Jul 2008 18:54:59 +0200	[thread overview]
Message-ID: <20080710165459.GA17542@rap.rap.dk> (raw)

I would like to know what is going on wrt resyncing, how it is done.
This is because I have some ideas to speed up the process. 
I have noted for a 4 drive raid10,f2 array that only about 25 % of the
IO speed is used during the rebuid, I would like to have something like
90 % as a goal.

This is especially for raid10,f2, where I think I can make it much
better, but posssibly also for other raid types, as input to an
explanation on the wiki of what is really going on. 

Are there references on the net? I tried to look but did not really find
something.

I don't really understand why resync is going on for raid10,f2.
But maybe it checks all of the array, and checks that the two copies are
identical. Is that so? I got some communication with Neil that some
writing is involved in the resync, I don't understand why. 

And what happens if a discrepancy is found? Which of the 2 copies are the
good one? Maybe one could look if there are any CRC errors, or disk read
retries going on. I could understand if it was a raid10,f3 - then if one
was different from the 2 other copies - you could correct the odd copy.

For raid5 and raid6 I could imagine that the parity blocks were cheked.

I could of cause read the code, but I would like an overview before
dwelving into that part.

best regards
keld

             reply	other threads:[~2008-07-10 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 16:54 Keld Jørn Simonsen [this message]
2008-07-10 17:45 ` resync'ing - what is going on Jon Nelson
2008-07-10 18:03 ` Andre Noll
2008-07-11  4:51 ` Neil Brown
2008-07-11 22:29   ` Keld Jørn Simonsen
2008-07-12 10:44     ` Neil Brown
2008-07-12 11:50       ` Keld Jørn Simonsen

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=20080710165459.GA17542@rap.rap.dk \
    --to=keld@dkuug.dk \
    --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).