From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC on mostly empty file system
Date: Tue, 9 Sep 2014 15:06:19 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.09.15.06.18@googlemail.com> (raw)
In-Reply-To: 3150960.nnNb4J6vhp@wuerfel
On Tue, 09 Sep 2014 16:29:05 +0200, Arnd Bergmann wrote:
> As I mentioned at the kernel summit, I have a file system that I use mostly
> for storing my one kernel git tree and occasionally some build trees
> (those are normally on a tmpfs), and I have again run into the problem
> where the file system is only partially full (I think 18% in this case)
> but I am unable to create new files.
You didn't give us any "btrfs fs show" or "btrfs fs df" outpu to look at,
so chances are that a lot of empty data chunks have made themselves
comfortable and prevent new metadata chunks from being allocated.
The usual fix is to run balance with -dusage=x, where 0 <= x <= ~20.
> The 82 MB image file is at
> https://drive.google.com/file/d/0B_XQwQ5KlfJAWDJfS1E0TG1CLTA/edit?usp=sharing
This is >780 MB..
-h
next prev parent reply other threads:[~2014-09-09 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 14:29 ENOSPC on mostly empty file system Arnd Bergmann
2014-09-09 15:06 ` Holger Hoffstätte [this message]
2014-09-09 15:12 ` Holger Hoffstätte
2014-09-09 18:18 ` Arnd Bergmann
2014-09-09 19:49 ` Clemens Eisserer
2014-09-09 19:56 ` Hugo Mills
2014-09-09 21:49 ` Arnd Bergmann
2014-09-09 21:57 ` Hugo Mills
2014-09-09 22:11 ` Roman Mamedov
2014-09-09 22:12 ` Arnd Bergmann
2014-09-09 22:23 ` Holger Hoffstätte
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.2014.09.09.15.06.18@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 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.