From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Best strategie to remove devices from pool
Date: Tue, 17 Oct 2017 22:57:27 +0000 (UTC) [thread overview]
Message-ID: <pan$9b46f$9dad1141$c719d4ab$389f4bee@cox.net> (raw)
In-Reply-To: 1508263135.2887.1.camel@cloud.haefemeier.eu
Cloud Admin posted on Tue, 17 Oct 2017 19:58:55 +0200 as excerpted:
> Hi,
> I want to remove two devices from a BTRFS RAID 1 pool. It should be
> enough free space to do it, but what is the best strategie. Remove both
> device in one call 'btrfs dev rem /dev/sda1 /dev/sdb1' (for example) or
> should it be better in two separate calls? What is faster? Are there
> other constraints to think about?
As a general policy, I'd first ensure that I had current backups in case
something goes wrong, unless of course you consider the data trivial
enough not to bother with backups. No sense unnecessarily tempting fate.
=:^\
Then I'd use the two devices in one call remove, because btrfs device
remove has an implicit rebalance that moves chunks off the device being
removed to the other available devices, and a rebalance can take awhile,
so doing two removals at once should go much faster than one at a time.
I'd also suggest that if you use btrfs quota functionality, you disable
it at least while doing the removes/balances, as trying to recalculate
the quotas constantly slows things down considerably, and if you have
lots of subvolume snapshots on the filesystem, I suggest you first delete
as many of those as you can reasonably delete (and turn off any scheduled
snapshotting during the remove/rebalance), as well, because they too can
slow down balances quite a bit.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-10-17 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 17:58 Best strategie to remove devices from pool Cloud Admin
2017-10-17 22:57 ` Duncan [this message]
2017-10-18 11:36 ` 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='pan$9b46f$9dad1141$c719d4ab$389f4bee@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).