All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: Ram Ramesh <rramesh2400@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 to raid6 reshape or recreate?
Date: Thu, 14 Aug 2014 14:06:11 +0800	[thread overview]
Message-ID: <53EC51D3.9020204@fnarfbargle.com> (raw)
In-Reply-To: <53EC36A8.7090308@gmail.com>

On 14/08/14 12:10, Ram Ramesh wrote:
> On 08/13/2014 10:29 PM, Brad Campbell wrote:
>> On 14/08/14 01:25, Ram Ramesh wrote:
>>
>>> On a slightly different topic, will it be faster after a disk
>>> fail/replacement as opposed to raid reshaping?
>>
>> Much.
>> I just re-striped a RAID6 changing the chunk size from 128k to 64k.
>> This took 12 days all up. It's the seeking that kills it. To replace a
>> disk or do a resync on the same array takes less than 10 hours.
>>
>>
>>
> I am curious. Why do you have to change chunk size? What is the
> benefit/advantage?

When I initially selected 128k it was for a stripe of 8 chunks (10 
disks) and for a workload that contained lots of fairly big streaming 
writes and reads.  The array has since grown to 12 chunks (14 disks) and 
the workload turned out to be a lot more random than I initially had 
profiled, so I re-striped to attempt to reduce the amount of RMW 
happening on the disks.

It may well be academic, but it's a lot easier to find 768k to write in 
one action than 1.5M.

... and probably because I could.


      reply	other threads:[~2014-08-14  6:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  1:05 Raid5 to raid6 reshape or recreate? Ram Ramesh
2014-08-13  9:02 ` Mikael Abrahamsson
2014-08-13 17:25 ` Ram Ramesh
2014-08-14  3:29   ` Brad Campbell
2014-08-14  4:10     ` Ram Ramesh
2014-08-14  6:06       ` Brad Campbell [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=53EC51D3.9020204@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rramesh2400@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 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.