linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: Brad Campbell <brad@wasp.net.au>,
	RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Basic RAID5/6 reshape question
Date: Tue, 16 Dec 2008 09:24:47 +1100	[thread overview]
Message-ID: <18758.55599.689845.935141@notabene.brown> (raw)
In-Reply-To: message from Roger Heflin on Thursday December 11

On Thursday December 11, rogerheflin@gmail.com wrote:
> 
> Reshaping appears to be much much slower.

Yes.

> 
> I can resync in just a 2-3 hours, but a reshape of a single drive 
> takes 10-15 hours with nothing else happening, if any other work is 
> being done by the disks the number gets much worse.

With resync, the drives a streaming - reading sequential blocks.
With reshape, they are reading from one place, and writing to
another.   It tries to maximise the size of the reads and writes and
so minimise seeks, but there is a limit to that.  If you increase the
stripe_cache_size that should increase the size of each read and write
and so might improve reshape speed a bit.


> 
> To make it look just like a normally built array of the same number of 
> disks it is very likely that reshaping is moving lots and lots of data 
> around to make the changes.

True.

> 
> I have so far done 2 reshapes, and I would like to know also how 
> dangerous an event would be if it happens during a reshape.

A drive failure or a system crash should be handled correctly.

NeilBrown

  reply	other threads:[~2008-12-15 22:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  9:55 Basic RAID5/6 reshape question Brad Campbell
2008-12-12  1:06 ` Ryan Wagoner
2008-12-12 19:17   ` Brad Campbell
2008-12-12 20:27     ` Justin Piszcz
2008-12-12  3:52 ` Roger Heflin
2008-12-15 22:24   ` Neil Brown [this message]
2008-12-15 22:20 ` Neil Brown

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=18758.55599.689845.935141@notabene.brown \
    --to=neilb@suse.de \
    --cc=brad@wasp.net.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@gmail.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).