From: Roman Mamedov <rm@romanrm.net>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Clemens Eisserer <linuxhippy@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC on mostly empty file system
Date: Wed, 10 Sep 2014 04:11:25 +0600 [thread overview]
Message-ID: <20140910041125.3fb1ac80@natsu> (raw)
In-Reply-To: <20140909215725.GE5783@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Tue, 9 Sep 2014 22:57:25 +0100
Hugo Mills <hugo@carfax.org.uk> wrote:
> On Tue, Sep 09, 2014 at 11:49:10PM +0200, Arnd Bergmann wrote:
> > Ok, now I'm in the bad state again (after running a 'make allmodconfig'
> > kernel build:
> >
> > Label: none uuid: 1d88cccb-3d0e-42d9-8252-a226dc5c2e47
> > Total devices 1 FS bytes used 8.79GB
> > devid 1 size 67.14GB used 67.14GB path /dev/sdc6
>
> All the space on the FS has been allocated to some purpose or other.
>
> > Data: total=65.11GB, used=7.99GB
>
> Here, you have 65 GiB allocated to data, but only 8 GiB of that
> used. The FS won't automatically free up any of that (yet -- it's one
> of the project ideas).
If you find yourself constantly running into this situation, rather than
incorporating periodical btrfs 'balances' into your scripts, you could consider
going with the "mixed" allocation mode of the FS, using the -M option of mkfs.
Seeing as this is not the largest-sized partition in the world in the first
place, the mixed mode would allow for a more efficient and flexible space
allocation on it; at the cost of some performance penalty (you could compare
your compilation times, but I don't think it's too significant).
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-09-09 22:20 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
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 [this message]
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=20140910041125.3fb1ac80@natsu \
--to=rm@romanrm.net \
--cc=arnd@arndb.de \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxhippy@gmail.com \
/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).