From: Mark Murawski <markm-lists@intellasoft.net>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs balance enospc
Date: Wed, 17 Sep 2014 13:51:51 -0400 [thread overview]
Message-ID: <5419CA37.1070608@intellasoft.net> (raw)
In-Reply-To: <BAY172-W49807D9D79231B7B004F04B0C90@phx.gbl>
> Does/should a balance imply removal of missing devices (as long as
the minimum number of devices are still available)?
That's a really good question. As a user I would expect it to balance
over remaining devices assuming you still have a complete picture.
Doing a device delete missing after a balance should be just some pool
metadata updates at that point.
Anyway... I solved my problem by moving/deleting files to free up space
to the point that balance no longer complained about enospc.
I suppose btrfs needs extra working space to do a balance... above and
beyond the actual size of the existing data/metadata to be moved? I had
a total of three devices, with what appeared to be plenty of space on
the two that were to be remaining, but balance/remove was still
complaining to be out of disk space.
It would be a good idea for some metrics to be calculated upon start of
a removal or balance to tell the user "hey you need to free up XXX more
bytes in order for this operation to be successful".
next prev parent reply other threads:[~2014-09-17 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54186A4B.60902@intellasoft.net>
2014-09-16 16:51 ` btrfs balance enospc Mark Murawski
2014-09-16 17:26 ` Chris Murphy
2014-09-16 19:54 ` Mark Murawski
2014-09-16 21:22 ` Chris Murphy
2014-09-16 20:10 ` Kyle Gates
2014-09-17 17:51 ` Mark Murawski [this message]
2014-09-17 19:10 ` Chris Murphy
2014-09-17 21:11 ` Duncan
2014-09-15 15:34 Mark Murawski
2014-09-15 17:07 ` Leonidas Spyropoulos
2014-09-15 17:37 ` Mark Murawski
2014-09-15 20:54 ` Chris Murphy
2014-09-15 22:40 ` Mark Murawski
2014-09-16 0:08 ` Duncan
2014-09-16 1:19 ` Chris Murphy
2014-09-16 2:23 ` Mark Murawski
2014-09-16 16:37 ` Duncan
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=5419CA37.1070608@intellasoft.net \
--to=markm-lists@intellasoft.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).