From: Michael Busby <michael.a.busby@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Converting from Raid 5 to 6
Date: Mon, 24 Oct 2011 21:47:19 +0100 [thread overview]
Message-ID: <CAFsPQ_-9BU_x_VKJSThTNhmQrcYZaoyJTfWgyGKVjhtEVe5-oA@mail.gmail.com> (raw)
In-Reply-To: <20111025073908.6d754588@notabene.brown>
I was sure i added the device before, but when rebooted the system it
has seemed to lose the extra drive and i had already restarted the
grow command with out checking the disk was there, so more than likely
a mistake by me
On 24 October 2011 21:39, NeilBrown <neilb@suse.de> wrote:
> On Mon, 24 Oct 2011 21:19:22 +0100 Michael Busby <michael.a.busby@gmail.com>
> wrote:
>
>> Ok thanks, i have 1 small issue, when added the extra disk its been
>> maked as spare, is this normal?
>>
>> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
>> [raid4] [raid10]
>> md0 : active raid6 sde[0] sdg[6](S) sda[4] sdb[3] sdd[2] sdc[1]
>> 7814055936 blocks super 1.0 level 6, 512k chunk, algorithm 18
>> [6/5] [UUUUU_]
>> [>....................] reshape = 3.0% (59244544/1953513984)
>> finish=11122.8min speed=2837K/sec
>>
>
> It looks like the extra drive was added after you started the grow.
>
> So it is still a spare.
> Once the grow finishes you will have a singly-degraded RAID6.
> Then it will immediately start recovering the missing device to the spare.
>
> Did you add the extra drive after starting the grow - or before??
>
> NeilBrown
>
>
>
>>
>>
>>
>> On 24 October 2011 21:14, NeilBrown <neilb@suse.de> wrote:
>> > On Mon, 24 Oct 2011 17:03:46 +0100 Michael Busby <michael.a.busby@gmail.com>
>> > wrote:
>> >
>> >> should the speed be very slow when doing this progress, its a lot
>> >> slower than a normal grow
>> >
>> > Yes.
>> > The array is being reshaped in-place. i.e. data is being read from part of
>> > the array, rearranged, and written back to the same part of the array.
>> > As you can imagine, this is risky - a crash will leave an inconsistent state.
>> > Hence the backup file. Everything in the array is first written to the
>> > backup file, then back to the array. So it is slow.
>> >
>> > A "normal" grow is writing to somewhere where there is no valid data, so it
>> > doesn't need the backup.
>> >
>> > I do have a plan to make this faster.... but I have lots of plans and little
>> > time.
>> >
>> > NeilBrown
>> >
>> >
>> >
>> >
>> >>
>> >> reshape = 1.2% (25006080/1953513984) finish=12481.8min speed=2574K/sec
>> >>
>> >> On 24 October 2011 15:11, Mathias Burén <mathias.buren@gmail.com> wrote:
>> >> > On 24 October 2011 14:11, Michael Busby <michael.a.busby@gmail.com> wrote:
>> >> >> At the moment i have a raid5 setup with 5 disks, i am looking to add a
>> >> >> 6th disk and change from raid 5 to raid 6
>> >> >>
>> >> >> having looked at Neil's site i have found the following command, and
>> >> >> just want to double check this is still the recommend way of
>> >> >> converting
>> >> >>
>> >> >> mdadm --grow /dev/md0 --level=6 --raid-disks=6 --backup-file=/home/md.backup
>> >> >>
>> >> >> also would i need to add the extra disk before or after the command?
>> >> >>
>> >> >> cheers
>> >> >> --
>> >> >> 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
>> >> >>
>> >> >
>> >> > Hi,
>> >> >
>> >> > I grew my 6 disk RAID5 to a 7 disk RAID6. First, add the drive. Then
>> >> > partition it as required. Then add the drive to the array (I think
>> >> > it'll become a spare?). Then you can grow it.
>> >> >
>> >> > Make sure you're using the latest mdadm tools available.
>> >> >
>> >> > Regards,
>> >> > Mathias
>> >> >
>> >> --
>> >> 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
next prev parent reply other threads:[~2011-10-24 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:11 Converting from Raid 5 to 6 Michael Busby
2011-10-24 14:11 ` Mathias Burén
2011-10-24 16:03 ` Michael Busby
2011-10-24 16:27 ` Mathias Burén
2011-10-24 16:34 ` Michael Busby
2011-10-24 20:14 ` NeilBrown
2011-10-24 20:19 ` Michael Busby
2011-10-24 20:39 ` NeilBrown
2011-10-24 20:47 ` Michael Busby [this message]
2013-11-30 22:13 ` Michael Busby
2013-12-02 5:51 ` NeilBrown
2013-12-02 15:07 ` Michael Busby
2013-12-02 20:38 ` NeilBrown
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=CAFsPQ_-9BU_x_VKJSThTNhmQrcYZaoyJTfWgyGKVjhtEVe5-oA@mail.gmail.com \
--to=michael.a.busby@gmail.com \
--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).