From: "Nigel J. Terry" <nigel@nigelterry.net>
To: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Cc: Tim <irule@irule.net>
Subject: Re: Raid5 reshape
Date: Fri, 16 Jun 2006 12:00:49 -0400 [thread overview]
Message-ID: <4492D5B1.60004@nigelterry.net> (raw)
In-Reply-To: <17554.21119.487820.638171@cse.unsw.edu.au>
Neil Brown wrote:
> On Thursday June 15, irule@irule.net wrote:
>
>> Hello all,
>>
>> I'm sorry if this is a silly question, but I've been digging around for
>> a few days now and have not found a clear answer, so I'm tossing it out
>> to those who know it best.
>>
>> I see that as of a few rc's ago, 2.6.17 has had the capability of adding
>> additional drives to an active raid 5 array (w/ the proper ver of mdadm,
>> of course). I cannot, however, for the life of me find out exactly how
>> one goes about doing it! I would love if someone could give a
>> step-by-step on what needs to be changed in, say, mdadm.conf (if
>> anything), and what args you need to throw at mdadm to start the reshape
>> process.
>>
>> As a point of reference, here's my current mdadm.conf:
>>
>>
>> DEVICE /dev/sda1
>> DEVICE /dev/sdb1
>> DEVICE /dev/sdc1
>> ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1,/dev/sdc1 level=5 num-devices=3
>>
>>
>
> May I suggest:
>
> DEVICE /dev/sd?1
> ARRAY /dev/md0 UUID=whatever
>
> it would be a lot safer.
>
>
>> I will be adding the devices /dev/sde1 and /dev/sdf1 (when I can find
>> out how :)
>>
>
> mdadm /dev/md0 --add /dev/sde1 /dev/sdf1
> mdadm --grow /dev/md0 --raid-disks=5
>
> 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
>
>
This might be an even sillier question, but I'll ask it anyway...
If I add a drive to my RAID5 array, what happens to the ext3 filesystem
on top of it? Does it grow automatically? Do I have to take some action
to use the extra space?
Thanks
Nigel
next prev parent reply other threads:[~2006-06-16 16:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 6:34 Raid5 reshape Tim
2006-06-16 6:41 ` Neil Brown
2006-06-16 16:00 ` Nigel J. Terry [this message]
2006-06-16 16:14 ` Tim T
2006-06-16 22:28 ` Neil Brown
2006-06-16 22:39 ` Nigel J. Terry
2006-06-16 22:44 ` Neil Brown
2006-06-17 19:21 ` Nigel J. Terry
2006-06-17 21:55 ` Neil Brown
2006-06-17 22:01 ` Nigel J. Terry
2006-06-17 22:05 ` Nigel J. Terry
2006-06-17 22:17 ` Neil Brown
2006-06-17 22:19 ` Nigel J. Terry
2006-06-18 12:57 ` Nigel J. Terry
2006-06-19 2:03 ` Neil Brown
2006-06-19 21:42 ` Nigel J. Terry
2006-06-19 22:46 ` Neil Brown
2006-06-19 22:53 ` Nigel J. Terry
2006-06-19 23:29 ` Mike Hardy
2006-06-19 23:33 ` Nigel J. Terry
2006-06-19 23:33 ` Neil Brown
2006-06-19 23:35 ` Nigel J. Terry
2006-06-20 10:35 ` Nigel J. Terry
2006-06-21 6:02 ` Neil Brown
2006-06-24 22:58 ` Raid5 reshape (Solved) Nigel J. Terry
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=4492D5B1.60004@nigelterry.net \
--to=nigel@nigelterry.net \
--cc=irule@irule.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).