From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: intermittent -ENOSPC errors on btrfs filesystem with 170G free
Date: Tue, 26 May 2015 18:57:48 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.05.26.18.57.48@googlemail.com> (raw)
In-Reply-To: CAJCQCtQsCU9OhSPRjqTS30i8KeC-_aa9SG+qmViA_q5po00QrQ@mail.gmail.com
On Tue, 26 May 2015 12:18:40 -0600, Chris Murphy wrote:
> Oh yeah easy to miss, but obvious once pointed out:
>
>> Data, single: total=227.94GiB, used=58.16GiB
>
> I thought we had automatic deallocation of unused chunks but I guess
> it hasn't landed yet.
It did (in 3.18 IIRC), but that doesn't help with - for whatever reason -
severely unbalanced chunks, i.e. all allocated but each used only a
little bit. Now, how and why that happened..
-h
next prev parent reply other threads:[~2015-05-26 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 17:36 intermittent -ENOSPC errors on btrfs filesystem with 170G free Lennert Buytenhek
2015-05-26 17:50 ` Chris Murphy
2015-05-26 18:02 ` Lennert Buytenhek
2015-05-26 18:08 ` Hugo Mills
2015-05-26 18:18 ` Chris Murphy
2015-05-26 18:50 ` Calvin Walton
2015-05-26 19:29 ` Chris Murphy
2015-05-26 18:57 ` Holger Hoffstätte [this message]
2015-06-09 10:54 ` Lennert Buytenhek
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.2015.05.26.18.57.48@googlemail.com \
--to=holger.hoffstaette@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox