RAID6 chunk size change?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: RAID6 chunk size change?

On Sun, Jan 23, 2011 at 10:53 AM, Mark Knecht wr=
ote:
> Hi,
>   I've got an existing (and well backed up as of a couple of min=
utes
> 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       =C2=
=A07        0      active sync  =
/dev/sda7
>       1       8       23=
       1      active sync   /d=
ev/sdb7
>       2       8       39=
       2      active sync   /d=
ev/sdc7
>       3       8       50=
       3      active sync   /d=
ev/sdd2
>       4       8       66=
       4      active sync   /d=
ev/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 somethi=
ng like:
>
> mdadm --grow /dev/md7 --level=3D6 --chunk=3D16 --backup-file=3D/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=3D16

would be enough.

Cheers,
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: RAID6 chunk size change?

--Sig_/oYQRnXKf_lfs3WrdtB6hG+U
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sun, 23 Jan 2011 11:10:40 -0800
Mark Knecht wrote:

> On Sun, Jan 23, 2011 at 10:53 AM, Mark Knecht wrot=
e:
> > Hi,
> >   I've got an existing (and well backed up as of a couple of minut=
es
> > 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 ho=
st c2stable)
> >           UUID : ded5e0c6:1a5a73ad:01949557:bb=
4e015a
> >         Events : 17
> >
> >    Number   Major   Minor   RaidDevice State
> >       0       8       =C2=
=A07        0      active sync   /d=
ev/sda7
> >       1       8       23 =
       1      active sync   /dev/sd=
b7
> >       2       8       39 =
       2      active sync   /dev/sd=
c7
> >       3       8       50 =
       3      active sync   /dev/sd=
d2
> >       4       8       66 =
       4      active sync   /dev/sd=
e2
> > c2stable ~ #
> >
> >   I would like to change this RAID to a smaller chunk size. (16K f=
or
> > 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=3D6 --chunk=3D16 --backup-file=3D/root/ba=
ckup-md7
> >
> > Maybe I don't need --level because the level isn't changing? Neither
> > is the number of drives.
> >
> > Thanks in advance,
> > Mark
> >
>=20
> OK, I found a blog of Neil's in which I had read the top but hadn't
> gone through the comments:
>=20
> http://neil.brown.name/blog/20090817000931
> It seems he answers my question further down in the comments.
>=20
> Looks like
>=20
> mdadm --grow /dev/md7 --chunk=3D16

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-chu nk-size-the-ben=
chmarks/

--=20
With respect,
Roman

--Sig_/oYQRnXKf_lfs3WrdtB6hG+U
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk08huQACgkQTLKSvz+PZwj86wCfaLb+4rl0vQPuji1CPt52 cMl6
OSgAnR6th65lIh/LwH9jHAVRb3BSyFWM
=WuNZ
-----END PGP SIGNATURE-----

--Sig_/oYQRnXKf_lfs3WrdtB6hG+U--
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: RAID6 chunk size change?

On Sun, Jan 23, 2011 at 11:52 AM, Roman Mamedov wrote:
> On Sun, 23 Jan 2011 11:10:40 -0800
> Mark Knecht wrote:

>>
>> 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-chu nk-size-the-benchmarks/
>
> --
> With respect,
> Roman
>
Thanks for the link. That's good information.

I have no strong preference for 16K other than I have two RAID6's on
this set of drives and the one that's 16K tests in iozone as about 2
times faster than the 512K one that I want to change.

I can certainly try 64K, see how it works out, and then do the reshape
again if necessary.

My work model for this drive is basically running VMware virtual
machines. The bulk of the files stored on this RAID are 2GB files. I
have no idea how VMware (or Virtualbox which I also us) makes use
those files other than they represent the virtual hard drive.

Again, thanks for the info.

Cheers,
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html