All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: bobzer <bobzer@gmail.com>, Peter Grandi <pg@lxra2.to.sabi.co.uk>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
Date: Sat, 6 Aug 2016 19:04:03 +0100	[thread overview]
Message-ID: <57A62693.5040209@youngman.org.uk> (raw)
In-Reply-To: <CADzS=aqLeMibSf-=U1+-_pcoGDu043exZ9ytUR6XLUwZ=VDOWw@mail.gmail.com>

On 06/08/16 00:32, bobzer wrote:
> thank you very much for all your help
> 
> I manage to borrow 2  3TB drive
> So i was thinking of dd copie my image to one, use the other to
> reconstruct my raid
> so at this point i got my first raid5 clean
> then i prepare my raid6 degraded with the the 3  4TB and do a rsync
> 
> another solution could be to move the image disk to one 3TB
> create the raid6 degraded with the 3 4TB
> move the image in the raid 6
> replace the 2 2TB with the 2 3TB (with a DD copy ?)
> reuse the 2 2TB to have a clean raid 6
> rsync from the degraded raid5 to the clean raid6
> 
> I prefere the first solution because the raid 5 is clean and so it
> should be safer but i worrying about the stress of rebuild the raid

Okay. So rebuilding a raid could tip it over the edge.

But you now have four spare drives. So the obvious solution is

create a new raid6 with 2 x 4TB and 2 x 3TB drives.
Copy from the old raid to the new one - the reads won't stress the old
raid anywhere near as much as a rebuild.
Replace one of the 3TB disks with the 4TB that's currently in the old raid.
Raid0 the 2 x 2TB disks from the old raid, and replace the second 3TB disk.

At no point are you rebuilding a degraded raid, and when your data is at
its greatest risk (no backup, raid reshaping) you have a raid6 so you
could survive a disk failure. Oh - and always use mdadm --replace so the
raid always has spare disks ...

If you want to do it in place, ddrescue the two 2TB drives on to the two
3TB drives, so again you can raid0 the 2 x 2TB together, but I think
that's still taking a risk.

Cheers,
Wol

  reply	other threads:[~2016-08-06 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 21:14 migration of raid 5 to raid 6 and disk of 2TB to 4TB bobzer
2016-07-25 22:48 ` Wols Lists
2016-07-25 23:08 ` Adam Goryachev
2016-07-26 18:33 ` Peter Grandi
2016-07-26 20:19   ` Wols Lists
2016-07-27  2:16     ` bobzer
2016-07-27 13:22       ` Peter Grandi
2016-07-27 13:44         ` Wols Lists
2016-07-27 14:57           ` Peter Grandi
2016-07-27 13:27       ` Anthony Youngman
2016-07-27 15:12       ` Peter Grandi
2016-08-05 23:32         ` bobzer
2016-08-06 18:04           ` Wols Lists [this message]
2016-07-27 12:55     ` Peter Grandi

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=57A62693.5040209@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=bobzer@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pg@lxra2.to.sabi.co.uk \
    /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.