From: John Robinson <john.robinson@anonymous.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Reshaping the length of devices
Date: Fri, 12 Mar 2010 16:54:41 +0000 [thread overview]
Message-ID: <4B9A71D1.108@anonymous.org.uk> (raw)
In-Reply-To: <678411.30301.qm@web51307.mail.re2.yahoo.com>
On 12/03/2010 15:18, Jon Hardcastle wrote:
>
>
> --- On Fri, 12/3/10, Asdo <asdo@shiftmail.org> wrote:
>
>> From: Asdo <asdo@shiftmail.org>
>> Subject: Reshaping the length of devices
>> To: "linux-raid" <linux-raid@vger.kernel.org>
>> Date: Friday, 12 March, 2010, 15:15
>> I am wondering... is it possible to
>> reshape the length of the underlying devices with MD raid?
>>
>> I mean like in the case one buys larger disks: after moving
>> the raid partitions to the new disks half of them is still
>> free. So one might want to extend the raid partitions to the
>> end of the disks instead of creating another array in the
>> free space.
>>
>> I have searched the linux-raid mailing list history but I
>> couldn't find this topic.
>>
>> Thanks in advance
>
> As long as the size of ALL underlying devices have increased you can --grow=MAX to the a multiple of the now smallest drive.
Hmm, that reminds me I was meaning to ask - before I have to go to a
customer's premises and try it - if I have a CentOS 5 system with 0.90
metadata and type fd partitions with RAID-5 over 3 discs, and I want to
grow it by replacing the drives, if I dd small partitions onto larger
ones and reboot, will the system recognise the RAID-5 - which now has
its metadata somewhere in the middle of the paritions not at the end -
so that I can then --grow?
Cheers,
John.
next prev parent reply other threads:[~2010-03-12 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 15:15 Reshaping the length of devices Asdo
2010-03-12 15:18 ` Jon Hardcastle
2010-03-12 16:54 ` John Robinson [this message]
2010-03-12 17:08 ` Majed B.
2010-03-12 17:37 ` John Robinson
2010-03-12 15:20 ` Majed B.
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=4B9A71D1.108@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.