From: "Majed B." <majedb@gmail.com>
To: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: Growing after replacing with larger discs
Date: Sun, 14 Mar 2010 00:00:04 +0300 [thread overview]
Message-ID: <70ed7c3e1003131300i4c2ed3dasafcbf49e44920fd1@mail.gmail.com> (raw)
In-Reply-To: <aebf5d971003131245m477d05dfpcb5f2c7dfcb0820a@mail.gmail.com>
Beolach,
That involves double the work!
On Sat, Mar 13, 2010 at 11:45 PM, Beolach <beolach@gmail.com> wrote:
> Forgot to send to the list...
>
> On Sat, Mar 13, 2010 at 13:42, Beolach <beolach@gmail.com> wrote:
>> On Fri, Mar 12, 2010 at 10:39, John Robinson
>> <john.robinson@anonymous.org.uk> wrote:
>>> Before I have to go to a customer's premises and try it, I wanted to ask if
>>> anyone had already done anything like this: I have a CentOS 5 system with
>>> 0.90 metadata and type fd partitions with RAID-5 over 3 discs. I want to
>>> grow it by replacing the drives. If I dd the small partitions onto larger
>>> ones on the new discs, then 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?
>>>
>>
>> I have no idea if this would actually work, but maybe try partitioning
>> the new, larger drives so the partitions are identical in size to the
>> old discs, copying the old discs to the new partitions, starting the
>> array with the new partitions, resizing the new partitions, and then
>> running --grow. If mdadm can re-check the size of the member devices
>> of a running array at --grow time, this might work, but if it only
>> checks member device sizes at creation or assemble time, then it
>> probably won't.
>>
>>
>> Good luck,
>> Conway S. Smith
>>
> --
> 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-13 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:39 Growing after replacing with larger discs John Robinson
2010-03-12 18:00 ` Majed B.
2010-03-12 18:04 ` John Robinson
2010-03-12 18:13 ` Majed B.
2010-03-12 18:09 ` Luca Berra
2010-03-13 15:18 ` John Robinson
2010-03-13 15:21 ` Majed B.
2010-03-13 18:13 ` John Robinson
2010-03-13 18:22 ` Majed B.
2010-03-15 15:17 ` Stefan /*St0fF*/ Hübner
[not found] ` <aebf5d971003131242q234a6c5ct441dd995a9c6a541@mail.gmail.com>
2010-03-13 20:45 ` Beolach
2010-03-13 21:00 ` 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=70ed7c3e1003131300i4c2ed3dasafcbf49e44920fd1@mail.gmail.com \
--to=majedb@gmail.com \
--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).