linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: George Spelvin <linux@horizon.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 syncing at 24 MB/s?
Date: Wed, 18 Apr 2012 15:37:48 +1000	[thread overview]
Message-ID: <20120418153748.2cbaef35@notabene.brown> (raw)
In-Reply-To: <20120418052235.27608.qmail@science.horizon.com>

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

On 18 Apr 2012 01:22:35 -0400 "George Spelvin" <linux@horizon.com> wrote:

> > Can you try an experiment for me (if you don't have anything useful on the
> > array yet)?
> > 
> > Stop the array.  Recreate it exactly the same way as before, and see if it
> > goes faster.  I think it might - at least until it got up to where it was up
> > to.
> 
> Um, unfortunately, I do (I didn't actually make the posting until after
> the sync finished), but it should actually be non-destructive to do that
> to an existing array, right?
> 
> It's just like deleting and re-creating a partition; as long as you're
> *damn* sure you kept the parameters the same, it's a no-op.  Right?

Should be - yes.  But some times it is best not to play with fire.
Up to you....

Alternately, look at /proc/diskstats for the member devices.

The first 4 numbers relate to reads (iOs, Merges, Sectors, ticks) and the next
4 to writes.

You will probably see about  3 times as many reads as writes.

RAID6 resync reads the whole stripe, checks the parity blocks, and if they
are wrong it writes them out.

If most of them are good - you should see streaming writes at the full speed
of the disk/bus/slowest-part.

If lots are not correct (which can be expected on a new array), you get lot
of 
    read - seek-backwards - write

sequences, which slow things down a lot.

NeilBrown


> 
> I still have the data on the backup drives, so it's "only" a day's
> lost work if I fry it (I did some reorganization as well as simple bulk
> copying), so it's not *deadly* dangerous...
> 
> Thank you for the response!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-04-18  5:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  4:35 RAID6 syncing at 24 MB/s? George Spelvin
2012-04-18  4:47 ` Jack Wang
2012-04-18  5:05 ` NeilBrown
2012-04-18  5:22   ` George Spelvin
2012-04-18  5:37     ` NeilBrown [this message]

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=20120418153748.2cbaef35@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux@horizon.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).