Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Mark Knecht <markknecht@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID6 chunk size change?
Date: Mon, 24 Jan 2011 00:52:04 +0500	[thread overview]
Message-ID: <20110124005204.71688cc2@natsu> (raw)
In-Reply-To: <AANLkTimRZgzDd5Na_F3XR8x6YE5wTyDjkBnQSCeCFbWe@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]

On Sun, 23 Jan 2011 11:10:40 -0800
Mark Knecht <markknecht@gmail.com> wrote:

> On Sun, Jan 23, 2011 at 10:53 AM, Mark Knecht <markknecht@gmail.com> wrote:
> > Hi,
> >   I've got an existing (and well backed up as of a couple of minutes
> > ago) 5-drive RAID6 shown here:
> >
> > c2stable ~ # mdadm --detail /dev/md7
> > /dev/md7:
> >        Version : 1.2
> >  Creation Time : Sun Jan 16 17:02:24 2011
> >     Raid Level : raid6
> >     Array Size : 395387904 (377.07 GiB 404.88 GB)
> >  Used Dev Size : 131795968 (125.69 GiB 134.96 GB)
> >   Raid Devices : 5
> >  Total Devices : 5
> >    Persistence : Superblock is persistent
> >
> >    Update Time : Sun Jan 23 10:25:41 2011
> >          State : clean
> >  Active Devices : 5
> > Working Devices : 5
> >  Failed Devices : 0
> >  Spare Devices : 0
> >
> >         Layout : left-symmetric
> >     Chunk Size : 512K
> >
> >           Name : c2stable:7  (local to host c2stable)
> >           UUID : ded5e0c6:1a5a73ad:01949557:bb4e015a
> >         Events : 17
> >
> >    Number   Major   Minor   RaidDevice State
> >       0       8        7        0      active sync   /dev/sda7
> >       1       8       23        1      active sync   /dev/sdb7
> >       2       8       39        2      active sync   /dev/sdc7
> >       3       8       50        3      active sync   /dev/sdd2
> >       4       8       66        4      active sync   /dev/sde2
> > c2stable ~ #
> >
> >   I would like to change this RAID to a smaller chunk size. (16K for
> > now) What is the right command to use?
> >
> >   From Google and the mdadm man pages I'm coming up with something like:
> >
> > mdadm --grow /dev/md7 --level=6 --chunk=16 --backup-file=/root/backup-md7
> >
> > Maybe I don't need --level because the level isn't changing? Neither
> > is the number of drives.
> >
> > Thanks in advance,
> > Mark
> >
> 
> OK, I found a blog of Neil's in which I had read the top but hadn't
> gone through the comments:
> 
> http://neil.brown.name/blog/20090817000931
> It seems he answers my question further down in the comments.
> 
> Looks like
> 
> mdadm --grow /dev/md7 --chunk=16

I suggest that you reconsider going with 16K, it is a suboptimal chunk size.
The older default of 64K seems to be the sweet spot, at least for RAID5/6:
http://louwrentius.com/blog/2010/05/linux-raid-level-and-chunk-size-the-benchmarks/

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-01-23 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 18:53 RAID6 chunk size change? Mark Knecht
2011-01-23 19:10 ` Mark Knecht
2011-01-23 19:52   ` Roman Mamedov [this message]
2011-01-23 20:16     ` Mark Knecht

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=20110124005204.71688cc2@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=markknecht@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