From: Gareth Pye <gareth@cerberos.id.au>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Drive Replacement
Date: Sat, 22 Oct 2016 09:03:16 +1100 [thread overview]
Message-ID: <CA+WRLO-XY2aai7z8436yna14cjbRsPrWgHwxbcf5Kq_-7RENCQ@mail.gmail.com> (raw)
I've got a BTRFS array that is of mixed size disks:
2x750G
3x1.5T
3x3T
And it's getting fuller than I'd like. The problem is that adding
disks is harder than one would like as the computer only has 8 sata
ports. Is it viable to do the following to upgrade one of the disks?
A) Take array offline
B) DD the contents of one of the 750G drives to a new 3T drive
C) Remove the 750G from the system
D) btrfs scan
E) Mount array
F) Run a balance
I know that not physically removing the old copy of the drive will
cause massive issues, but if I do that everything should be fine
right?
--
Gareth Pye - chatterofjudges.mtgmelb.com
Level 2 MTG Judge, Melbourne, Australia
next reply other threads:[~2016-10-21 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 22:03 Gareth Pye [this message]
2016-10-21 22:07 ` Drive Replacement Hugo Mills
2016-10-21 22:13 ` Peter Becker
2016-10-24 11:47 ` Austin S. Hemmelgarn
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=CA+WRLO-XY2aai7z8436yna14cjbRsPrWgHwxbcf5Kq_-7RENCQ@mail.gmail.com \
--to=gareth@cerberos.id.au \
--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;
as well as URLs for NNTP newsgroup(s).