From: "Majed B." <majedb@gmail.com>
To: Asdo <asdo@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Reshaping the length of devices
Date: Fri, 12 Mar 2010 18:20:39 +0300 [thread overview]
Message-ID: <70ed7c3e1003120720q6e2e9b7bxf2f66fdb8cb892e2@mail.gmail.com> (raw)
In-Reply-To: <4B9A5A7B.4070105@shiftmail.org>
I think it depends on how you migrate to the new disks. The best
option would be to have one partition use all the space on the new
(larger) disks, and replace a disk in the array with the new disk &
wait for it to sync. Do the same for all disks.
You'll end up with a working array, where each disk has 1 partition
but the total size of the array is only consuming half the capacity.
After that just use --growth and it'll expand the array to the max
available capacity from the disks.
On Fri, Mar 12, 2010 at 6:15 PM, Asdo <asdo@shiftmail.org> wrote:
> 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
> --
> 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
>
--
Majed B.
--
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
prev parent reply other threads:[~2010-03-12 15:20 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
2010-03-12 17:08 ` Majed B.
2010-03-12 17:37 ` John Robinson
2010-03-12 15:20 ` Majed B. [this message]
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=70ed7c3e1003120720q6e2e9b7bxf2f66fdb8cb892e2@mail.gmail.com \
--to=majedb@gmail.com \
--cc=asdo@shiftmail.org \
--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 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).