From: Roman Mamedov <rm@romanrm.net>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Cloud Admin <admin@cloud.haefemeier.eu>, linux-btrfs@vger.kernel.org
Subject: Re: Best Practice: Add new device to RAID1 pool
Date: Mon, 24 Jul 2017 19:08:08 +0500 [thread overview]
Message-ID: <20170724190808.148964a6@natsu> (raw)
In-Reply-To: <18d96f74-00a8-9bb9-dddc-f50940d0971e@gmail.com>
On Mon, 24 Jul 2017 09:46:34 -0400
"Austin S. Hemmelgarn" <ahferroin7@gmail.com> wrote:
> > I am a little bit confused because the balance command is running since
> > 12 hours and only 3GB of data are touched. This would mean the whole
> > balance process (new disc has 8TB) would run a long, long time... and
> > is using one cpu by 100%.
>
> Based on what you're saying, it sounds like you've either run into a
> bug, or have a huge number of snapshots
...and possibly quotas (qgroups) enabled. (perhaps automatically by some tool,
and not by you). Try:
btrfs quota disable <mountpoint>
With respect,
Roman
next prev parent reply other threads:[~2017-07-24 14:08 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 [this message]
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
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=20170724190808.148964a6@natsu \
--to=rm@romanrm.net \
--cc=admin@cloud.haefemeier.eu \
--cc=ahferroin7@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.