From: Hugo Mills <hugo@carfax.org.uk>
To: Daniel Pocock <daniel@pocock.pro>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID1 migrate to bigger disks
Date: Sat, 24 Jan 2015 14:36:32 +0000 [thread overview]
Message-ID: <20150124143632.GF1654@carfax.org.uk> (raw)
In-Reply-To: <54C3AD0C.7080407@pocock.pro>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Sat, Jan 24, 2015 at 03:32:44PM +0100, Daniel Pocock wrote:
>
>
>
> I've got a RAID1 on two 1TB partitions, /dev/sda3 and /dev/sdb3
>
> I'm adding two new disks, they will have bigger partitions /dev/sdc3 and
> /dev/sdd3
>
> I'd like the BtrFs to migrate from the old partitions to the new ones as
> safely and quickly as possible and if it is reasonable to do so, keeping
> it online throughout the migration.
>
> Should I do the following:
>
> btrfs device add /dev/sdc3 /dev/sdd3 /mnt/btrfs0
> btrfs device delete /dev/sda3 /dev/sdb3 /mnt/btrfs0
>
> or should I do it this way:
>
> btrfs device add /dev/sdc3 /mnt/btrfs0
> btrfs device delete /dev/sda3 /mnt/btrfs0
> btrfs device add /dev/sdd3 /mnt/btrfs0
> btrfs device delete /dev/sdb3 /mnt/btrfs0
>
> or is there some other way to go about it?
btrfs replace start /dev/sda3 /dev/sdc3 /mountpoint
btrfs fi resize 3:max /mountpoint
btrfs replace start /dev/sdb3 /dev/sdd3 /mountpoint
btrfs fi resize 4:max /mountpoint
The 3 and 4 in the resize commands should be the devid of the
newly-added device.
Hugo.
--
Hugo Mills | I'll take your bet, but make it ten thousand francs.
hugo@... carfax.org.uk | I'm only a _poor_ corrupt official.
http://carfax.org.uk/ |
PGP: 65E74AC0 | Capt. Renaud, Casablanca
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-01-24 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 14:32 RAID1 migrate to bigger disks Daniel Pocock
2015-01-24 14:36 ` Hugo Mills [this message]
2015-01-24 14:46 ` Daniel Pocock
2015-01-24 15:47 ` Martin Steigerwald
2015-01-25 5:07 ` Paul Jones
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=20150124143632.GF1654@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=daniel@pocock.pro \
--cc=linux-btrfs@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