All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jonathan@infinitedepth.com.au" <jonathan@infinitedepth.com.au>
To: stan@hardwarefreak.com, NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 to raid6 - reshape very slow
Date: Tue, 29 May 2012 19:59:37 +1000	[thread overview]
Message-ID: <4FC49E09.3090302@infinitedepth.com.au> (raw)
In-Reply-To: <4FC478FA.2020100@hardwarefreak.com>

I suspected the only move was to wait it out.

Thanks for the feedback Stan & Neil.

On 29/05/2012 5:21 PM, Stan Hoeppner wrote:
> On 5/28/2012 7:56 PM, NeilBrown wrote:
>> On Tue, 29 May 2012 10:33:52 +1000 Jonathan Molyneux
>> <jonathan@infinitedepth.com.au>  wrote:
>>> md1 : active raid6 sde1[0] sdb1[6] sdh1[5] sdc1[4] sdg1[3] sdd1[2] sdf1[1]
>>>         7325679680 blocks super 0.91 level 6, 64k chunk, algorithm 18
>>> [7/6] [UUUUUU_]
>>>         [=========>...........]  reshape = 47.0% (689413888/1465135936)
>>> finish=4126.9min speed=3132K/sec
>> The only thing to do is to wait.  This is very much a seek-bound operation
>> and there is little room for making it go faster.
> With SSDs you'd see the throughput of this operation increase by 2
> orders of magnitude (100x) or more, as SSDs have application level seek
> latency of ~50-80 microseconds, over 100x lower than rotational drives
> which are in the 10-30 millisecond range depending on spindle speed.
>
> Of course, cost/GB for the same total storage is 2 to 10 times higher
> with SSD.  Though interestingly the price of SSDs continues to fall,
> whereas the rotational drive manufacturers are currently keeping drive
> prices artificially high, between 50-100% higher than last year
> depending on drive model, in an effort to recoup apparent financial
> losses caused by the flooding in Thailand.
>

  reply	other threads:[~2012-05-29  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29  0:33 raid5 to raid6 - reshape very slow Jonathan Molyneux
2012-05-29  0:56 ` NeilBrown
2012-05-29  7:21   ` Stan Hoeppner
2012-05-29  9:59     ` jonathan [this message]
2012-05-29 14:44       ` Alexander Kühn

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=4FC49E09.3090302@infinitedepth.com.au \
    --to=jonathan@infinitedepth.com.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=stan@hardwarefreak.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 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.