From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Balance fails with unallocated diskspace
Date: Wed, 15 Jun 2016 15:21:03 +0000 (UTC) [thread overview]
Message-ID: <pan$ea7fd$2f56e349$db0ce34a$6e2e77cd@cox.net> (raw)
In-Reply-To: CALy3tB28Kx6aHTj+B-g68foh2bKSb0cnPcy7D-QQw3WPb9Wz4Q@mail.gmail.com
Nisse Karlsson posted on Wed, 15 Jun 2016 11:58:36 +0200 as excerpted:
> Since I have about 1.5TB unallocated space it's my understanding that
> this shouldn't be a problem, or am I completely wrong?
Quick partial answer...
It's not just unallocated space in total that matters, but also the
number of devices with unallocated space. To write raid10 chunks
requires four devices. To write raid1 chunks requires two.
However, your usage output does indicate several hundred gigs of
unallocated space on multiple devices, so convert to raid1 shouldn't be
ENOSPCing... That it is would indicate a bug. There have been various
bugs of this sort, but I'm just a list regular, not a dev, and I'm not
sure of the current status, whether any such bugs are currently known or
not.
You don't mention kernel version in your post and I don't have time to
look up the bug ATM, but you might try the latest 4.1 and 4.4 LTS kernels
as well as the latest 4.6 and 4.7-rc kernels to see if it makes a
difference. If it's a problem with 4.6 and 4.7-rc then it becomes
interesting, and if it works with 4.4 or 4.1, even more so.
--
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:[~2016-06-15 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALy3tB3YaTAYrZLhA7X0CTCUNLm7JCAyVX0WSdp1K48TNfFAUA@mail.gmail.com>
2016-06-15 9:58 ` Balance fails with unallocated diskspace Nisse Karlsson
2016-06-15 13:06 ` Nisse Karlsson
2016-06-15 15:21 ` Duncan [this message]
[not found] ` <CAJCQCtQrBegWBCfM6nqfqNc5u-3M-7pdRn3Wf370oL-MXh9uiQ@mail.gmail.com>
2016-06-15 16:00 ` Nisse Karlsson
2016-06-15 16:29 ` Chris Murphy
2016-06-16 17:11 ` Nisse Karlsson
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$ea7fd$2f56e349$db0ce34a$6e2e77cd@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 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.