From: Martin Steigerwald <martin@lichtvoll.de>
To: Daniel Pocock <daniel@pocock.pro>
Cc: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: RAID1 migrate to bigger disks
Date: Sat, 24 Jan 2015 16:47:49 +0100 [thread overview]
Message-ID: <1427188.PHcY3qXV8q@merkaba> (raw)
In-Reply-To: <54C3B03E.8080002@pocock.pro>
Am Samstag, 24. Januar 2015, 15:46:22 schrieb Daniel Pocock:
> On 24/01/15 15:36, Hugo Mills wrote:
> > 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.
>
> Thanks for the fast reply
>
> In the event of power failure, can I safely shutdown the server during
> this operation and resume after starting again?
>
> I get more than 2 hours runtime from the UPS but I suspect that
> migrating 1TB will take at least 12 hours.
You can at least cancel the replacing:
merkaba:~> btrfs replace --help
usage: btrfs replace <command> [<args>]
btrfs replace start [-Bfr] <srcdev>|<devid> <targetdev> <mount_point>
Replace device of a btrfs filesystem.
btrfs replace status [-1] <mount_point>
Print status and progress information of a running device replace
btrfs replace cancel <mount_point>
Cancel a running device replace operation.
I thought you could resume it then later, but I don't see this. The man
page doesn't see it either.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2015-01-24 15:47 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
2015-01-24 14:46 ` Daniel Pocock
2015-01-24 15:47 ` Martin Steigerwald [this message]
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=1427188.PHcY3qXV8q@merkaba \
--to=martin@lichtvoll.de \
--cc=daniel@pocock.pro \
--cc=hugo@carfax.org.uk \
--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