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: Sun, 26 Feb 2012 15:05:53 -0500 [thread overview]
Message-ID: <jie3b2$v5d$1@dough.gmane.org> (raw)
In-Reply-To: <4F4A8D7A.5070605@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On 12-02-26 02:52 PM, Daniel Lee wrote:
> What's mysterious about that?
What's mysterious about needing to grow the filesystem to over 20GB to
unpack 10MB of (small, so yes, many) files?
> When you shrink it btrfs is going to throw
> away unused data to cram it all in the requested space and you had empty
> space that was taken up by the metadata allocation.
The shrinking is secondary mystery. It's the need for more than 20GB of
space for less than 3GB of files that's the major mystery.
> Did you compare
> btrfs fi df after you shrank it with before?
I didn't unfortunately.
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-26 20:05 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
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 [this message]
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='jie3b2$v5d$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).