linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Per Lindstrand <mail@perlindstrand.com>
To: Neil Brown <neilb@suse.de>
Cc: Patrik Jonsson <patrik@ucolick.org>, linux-raid@vger.kernel.org
Subject: Re: Raid5 resize "testing opportunity"
Date: Fri, 19 May 2006 22:11:44 +0200	[thread overview]
Message-ID: <446E2680.9070905@perlindstrand.com> (raw)
In-Reply-To: <17517.5342.472654.391841@cse.unsw.edu.au>

Hi Neil,

I'm currently running an active raid5 array of 12 x 300GB SATA devices.
During the last couple of months I have grown my raid two times (from 4
to 8 to 12). I was using a 2.6.16-rc1 kernel with the (at that time)
latest md-patch.

I'm happy to say that both times the growing procedure completed
successfully!

This is how I did:

At first I had 4 devices ( /dev/sd{a,b,c,d} ) running in an active raid5
array (chunk-size 256). When I bought 4 more I thought I’d try to grow
them instead of running another array. I assembled my array with 4
drives and made sure that the array started without problems (cat:ed
/proc/mdstat). After that I cfdisk:ed the 4 new devices to one huge
partition with the type FD (Linux raid autodetect) and added them as
spares with the command:

# mdadm --add /dev/md0 /dev/sd{e,f,g,h}1

After that I checked the /proc/mdstat to confirm that they had been
successfully added and then executed the grow command:

# mdadm -Gv /dev/md0 -n8

which started the whole growing procedure. After that I waited (it took
about 6 times rebuilding from 4 to 8 and almost 11 hours from 8 to 12).


The following information might not belong in the raid-list but I
thought it might be useful someone:
---------------------------------------------------------------------
The raid is encrypted with LUKS aes-cbc-essiv:sha256 and has an ext3
filesystem formatted with '-T Largefile', -m0 and '-R stride=64'. After
I successfully had grown the raid5 array I managed to resize the LUKS
and the ext3 partition with the following commands:

(After decrypting the raid using standard luksOpen procedure)

# cryptsetup resize cmd0
(no I didn't forget the <size> information)

# resize2fs -p /dev/mapper/cmd0
seemed to do the trick with the ext3 filesystem.
---------------------------------------------------------------------

This is how I did it both times and I must say, even though it was scary
as hell growing a raid of 2.1TB with need-to-have data, it was really
interesting and boy am I glad it worked! =)

I just thought I’d tribute to the raid-list with my grow-story. It can
be nice to hear of those who succeed too and not only when people have
accidents. =)

Thanks for a great work with the growing code!

Best regards
Per Lindstrand, Sweden

Neil Brown wrote:
> On Thursday May 18, patrik@ucolick.org wrote:
>> Hi Neil,
>>
>> The raid5 reshape seems to have gone smoothly (nice job!), though it
>> took 11 hours! Are there any pieces of info you would like about the array?
> 
> Excellent!
> 
> No, no other information would be useful.  
> This is the first real-life example that I know of of adding 2 devices
> at once.  That should be no more difficult, but it is good to know
> that it works in fact as well as in theory.
> 
> Thanks,
> NeilBrown
> -
> 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
-
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

  reply	other threads:[~2006-05-19 20:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  5:29 [PATCH 000 of 11] md: Introduction - assort md enhancements for 2.6.18 NeilBrown
2006-05-01  5:30 ` [PATCH 001 of 11] md: Reformat code in raid1_end_write_request to avoid goto NeilBrown
2006-05-01  5:30 ` [PATCH 002 of 11] md: Remove arbitrary limit on chunk size NeilBrown
2006-05-01  5:30 ` [PATCH 003 of 11] md: Remove useless ioctl warning NeilBrown
2006-05-01  5:30 ` [PATCH 004 of 11] md: Increase the delay before marking metadata clean, and make it configurable NeilBrown
2006-05-01  5:44   ` Andrew Morton
2006-05-01  6:02     ` Neil Brown
2006-05-01  6:13       ` Andrew Morton
2006-05-01 15:17         ` Linus Torvalds
2006-05-01  6:15       ` Nick Piggin
2006-05-02  5:56   ` bert hubert
2006-05-09  1:40     ` Neil Brown
2006-05-01  5:30 ` [PATCH 006 of 11] md: Remove nuisance message at shutdown NeilBrown
2006-05-01  5:30 ` [PATCH 007 of 11] md: Allow checkpoint of recovery with version-1 superblock NeilBrown
2006-05-01  5:30 ` [PATCH 008 of 11] md: Allow a linear array to have drives added while active NeilBrown
2006-05-01  5:30 ` [PATCH 009 of 11] md: Support stripe/offset mode in raid10 NeilBrown
2006-05-02 16:38   ` Al Boldi
2006-05-03  0:05     ` Neil Brown
2006-05-03  4:00       ` Al Boldi
2006-05-08  7:17         ` Neil Brown
2006-05-08 16:59           ` Al Boldi
2006-05-17 21:32           ` Raid5 resize "testing opportunity" Patrik Jonsson
2006-05-17 23:49             ` Neil Brown
2006-05-19  0:40               ` Patrik Jonsson
2006-05-19  0:44                 ` Neil Brown
2006-05-19 20:11                   ` Per Lindstrand [this message]
2006-05-01  5:31 ` [PATCH 010 of 11] md: make md_print_devices() static NeilBrown
2006-05-01  5:31 ` [PATCH 011 of 11] md: Split reshape portion of raid5 sync_request into a separate function NeilBrown
     [not found] ` <1060501053025.22961@suse.de>
2006-05-01  5:40   ` [PATCH 005 of 11] md: Merge raid5 and raid6 code H. Peter Anvin

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=446E2680.9070905@perlindstrand.com \
    --to=mail@perlindstrand.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=patrik@ucolick.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).