linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Svist <fry.kun@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: Changing Chunk Size on Array
Date: Mon, 19 Jul 2010 17:17:14 -0700	[thread overview]
Message-ID: <4C44EB0A.2060604@gmail.com> (raw)
In-Reply-To: <20100720014955.529eb9ca@notabene>

  On 07/19/2010 04:49 PM, Neil Brown wrote:
> On Sat, 17 Jul 2010 16:15:55 -0500
> "Leslie Rhorer"<lrhorer@satx.rr.com>  wrote:
>
>> 	I'm thinking about changing the chunk size on one of my arrays in
>> order to potentially improve performance.  The man page rather suggests -c
>> is a vlaid option under Grow mode, although it doesn't specifically say
>> mdadm supports it under --grow.  Is it indeed supported under mdadm 2.6.7.2
>> and kernel 2.6.26-2?  Assuming so, I would like to know a bit more about the
>> change before issuing the command.  Speficialy, what are the details of the
>> process?  Does the entire (RAID 6) array have to be re-written, such as is
>> the case with adding a drive to the array?  Does the recovery start
>> immediately?  Can it be interrupted and then continue at a later time?
> Yes, you can change chunksize with --grow.
> I think you need mdadm-3.1.2 and kernel 2.6.32 though (version numbers might
> not be accurate, but are close).
>
> Yes, the entire array gets re-written just like adding an extra device.
> The reshape does start immediately.
> If you shutdown or crash, then on restart the reshape will pick up where it
> left off.

I ran mine with mdadm v3.1.2 on 2.6.33.6-147.fc13.x86_64 (Fedora)
Too bad I screwed up the FS by shrinking the array too much beforehand - 
now I have no idea whether it would've worked or not.


  reply	other threads:[~2010-07-20  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17 21:15 Changing Chunk Size on Array Leslie Rhorer
2010-07-17 21:30 ` Roman Mamedov
2010-07-17 21:45   ` Leslie Rhorer
2010-07-19 23:49 ` Neil Brown
2010-07-20  0:17   ` Konstantin Svist [this message]
2010-07-21  5:52   ` Leslie Rhorer

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=4C44EB0A.2060604@gmail.com \
    --to=fry.kun@gmail.com \
    --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 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).