From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-btrfs@vger.kernel.org
Subject: Re: filesystem full when it's not? out of inodes? huh?
Date: Sat, 25 Feb 2012 21:16:40 -0500 [thread overview]
Message-ID: <jic4m8$j6g$1@dough.gmane.org> (raw)
In-Reply-To: <4F499498.1040006@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On 12-02-25 09:10 PM, Fahrzin Hemmati wrote:
> btrfs is horrible for small filesystems (like a 5GB drive). df -h says
> you have 967MB available,
So does dd. It manages to write that 967MB before getting an ENOSPC.
> but btrfs (at least by default) allocates 1GB
> at a time to data/metadata.
Bleah.
> This means that your 10MB file
It's a package of kernel headers so not a 10MB file but 10MB of lots of
small files, so heavy metadata allocation.
> is too big
> for the current allocation and requires a new data chunk, or another
> 1GB, which you don't have.
I see.
> Others might know of a way of changing the allocation size to less than
> 1GB, but otherwise I recommend switching to something more stable like
> ext4/reiserfs/etc.
So btrfs is still not yet suitable to be a root/usr/var filesystem, even
in kernel 3.0.0?
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-26 2:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 1:55 filesystem full when it's not? out of inodes? huh? Brian J. Murrell
2012-02-26 2:10 ` Fahrzin Hemmati
2012-02-26 2:16 ` Brian J. Murrell [this message]
2012-02-26 2:37 ` Fahrzin Hemmati
2012-02-26 3:57 ` Brian J. Murrell
2012-02-26 4:05 ` Fahrzin Hemmati
2012-03-09 22:02 ` Johannes Hirte
2012-02-26 8:52 ` Duncan
2012-02-26 9:10 ` Helmut Hullen
2012-02-26 9:41 ` Duncan
2012-03-03 10:25 ` Chris Samuel
2012-02-26 5:45 ` Brian J. Murrell
2012-02-26 5:50 ` Fahrzin Hemmati
2012-02-26 6:14 ` Brian J. Murrell
2012-02-26 7:19 ` Jérôme Poulin
2012-02-26 19:43 ` Brian J. Murrell
2012-02-26 11:00 ` Hugo Mills
2012-03-02 11:50 ` Brian J. Murrell
2012-03-02 12:23 ` Fajar A. Nugraha
2012-02-26 19:37 ` Daniel Lee
2012-02-26 19:48 ` Brian J. Murrell
2012-02-26 19:52 ` Daniel Lee
2012-02-26 20:05 ` Brian J. Murrell
2012-02-26 20:25 ` Daniel Lee
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='jic4m8$j6g$1@dough.gmane.org' \
--to=brian@interlinx.bc.ca \
--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).