All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Speed up reshape? (was Re: Cancel reshape?)
Date: Wed, 12 Jan 2011 17:02:11 +1100	[thread overview]
Message-ID: <20110112170211.3e88fdcb@notabene.brown> (raw)
In-Reply-To: <4D2D41E4.1000109@anonymous.org.uk>

On Wed, 12 Jan 2011 05:53:40 +0000 John Robinson
<john.robinson@anonymous.org.uk> wrote:

> On 12/01/2011 05:32, NeilBrown wrote:
> > On Wed, 12 Jan 2011 04:49:35 +0000 John Robinson
> > <john.robinson@anonymous.org.uk>  wrote:
> [...]
> >> Perhaps I can stop the reshape and restart it with the backup file
> >> elsewhere. Hmm, I've an SSD I haven't installed yet... Maybe time to
> >> give it a wee workout :-)
> >
> > That should work.
> >
> >   mdadm --stop ...
> >   copy file
> >   mdadm --assemble ...... --backup-file=/new/place
> 
> Yup. Not much of an improvement, though; the reshape is now running at 
> ~10MB/s instead of ~6.5MB/s, so ~27 hours to go instead of ~40 hours.
> 
> iostat tells me the original 3 discs are doing ~120 transactions per 
> second, reading ~20MB/s and writing ~10MB/s, while the one new disc is 
> doing ~60 tps, reading nothing (obviously) and writing ~10MB/s and the 
> backup (SSD) is doing ~45 tps and writing ~20MB/s. ~120tps sounds about 
> right for 120 seeks, 60 reads and 60 writes, and would explain the 
> speed, but otherwise this looks odd to me - why are we reading ~60MB/s 
> in total and writing ~40MB/s? I'd have expected to be reading less than 
> we're writing. And why are we apparently reading and writing in blocks 
> of under 512KB per device, when the backup file is 32MB? Is there 
> something I can tweak to run the reshape in bigger chunks? 
> sync_speed_min is already 200000...

1/ everything is read twice, once to back it up, once to relocate it.
  That is unfortunate, but awkward to avoid.

2/ try increasing the stripe_cache_size - it might help.

NeilBrown


> 
> Currently running SystemRescueCD 2.0.0, 32-bit kernel 2.6.35 and mdadm 
> 3.1.4. CPU usage is 2% system, 4% iowait.
> 
> Cheers,
> 
> John.


  reply	other threads:[~2011-01-12  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12  4:19 Cancel reshape? John Robinson
2011-01-12  4:49 ` NeilBrown
2011-01-12  4:49 ` John Robinson
2011-01-12  5:32   ` NeilBrown
2011-01-12  5:53     ` Speed up reshape? (was Re: Cancel reshape?) John Robinson
2011-01-12  6:02       ` NeilBrown [this message]
2011-01-13 13:44         ` John Robinson
2011-01-13 19:14           ` John Robinson

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=20110112170211.3e88fdcb@notabene.brown \
    --to=neilb@suse.de \
    --cc=john.robinson@anonymous.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.