From: Adam Borowski <kilobyte@angband.pl>
To: Chris Murphy <lists@colorremedies.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Cloud Admin <admin@cloud.haefemeier.eu>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Best Practice: Add new device to RAID1 pool
Date: Mon, 24 Jul 2017 23:17:58 +0200 [thread overview]
Message-ID: <20170724211758.zhgzyk5p2zzkcbog@angband.pl> (raw)
In-Reply-To: <CAJCQCtTpdn0zNmogkbDr0h4RjNvb8u21w7Sj3xjUrj77A+ss8w@mail.gmail.com>
On Mon, Jul 24, 2017 at 02:55:00PM -0600, Chris Murphy wrote:
> Egads.
>
> Maybe Cloud Admin ought to consider using a filter to just balance the
> data chunks across the three devices, and just leave the metadata on
> the original two disks?
Balancing when adding a new disk isn't that important unless the two old
disks are almost full.
> Maybe
> sudo btrfs balance start -dusage=100 <mp>
Note that this doesn't mean "all data", merely "all data chunks < 100%
full". It's a strictly-lesser-than comparison.
You'd want "-dusage=101" which is illegal, the right one is "-d". I used to
believe -dusage=100 does that, myself.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
next prev parent reply other threads:[~2017-07-24 21:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 11:27 Best Practice: Add new device to RAID1 pool Cloud Admin
2017-07-24 13:46 ` Austin S. Hemmelgarn
2017-07-24 14:08 ` Roman Mamedov
2017-07-24 16:42 ` Cloud Admin
2017-07-24 14:12 ` Cloud Admin
2017-07-24 14:25 ` Austin S. Hemmelgarn
2017-07-24 16:40 ` Cloud Admin
2017-07-29 23:04 ` Best Practice: Add new device to RAID1 pool (Summary) Cloud Admin
2017-07-31 11:52 ` Austin S. Hemmelgarn
2017-07-24 20:35 ` Best Practice: Add new device to RAID1 pool Chris Murphy
2017-07-24 20:42 ` Hugo Mills
2017-07-24 20:55 ` Chris Murphy
2017-07-24 21:00 ` Hugo Mills
2017-07-24 21:17 ` Adam Borowski [this message]
2017-07-24 23:18 ` Chris Murphy
2017-07-25 17:56 ` Cloud Admin
2017-07-24 21:12 ` waxhead
2017-07-24 21:20 ` Chris Murphy
2017-07-25 2:22 ` Marat Khalili
2017-07-25 8:13 ` Chris Murphy
2017-07-25 17:46 ` Cloud Admin
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=20170724211758.zhgzyk5p2zzkcbog@angband.pl \
--to=kilobyte@angband.pl \
--cc=admin@cloud.haefemeier.eu \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).