From: Michael Raskin <7c6f434c@mail.ru>
To: linux-btrfs@vger.kernel.org
Subject: [MISFEATURE] Size reporting on small devices
Date: Wed, 06 May 2009 20:53:29 +0400 [thread overview]
Message-ID: <4A01C089.2080201@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
During testing, I tried to create small BtrFS images (256M, 1G) and
just fill them up with large (100M) files. During these tests df -h
showed 130M at the time BtrFS reported "disk is full".
/dev/loop2 1.0G 895M 130M 88% /root/mnt/loop
One-byte files (80K+) allow to reproduce
/dev/loop2 1.0G 49M 976M 5% /root/mnt/loop
(and disk-full behavior) with Kernel BUG in
__btrfs_reserve_extent+0x351/0x35f , but that seems to be well-known.
Maybe df -i could be useful until metadata/data split is flexible? Is
there any way to inspect the metadata filling up and change the split?
Michael Raskin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEcBAEBAgAGBQJKAcCIAAoJEE6tnN0aWvw3VooH/RLHZrjk4DAsAWOt/H/3OvUb
+HPPpkbCjTwPwpBd+ckRe0abKpwhcisJJg9BSpF/Co3kRlwSKkwj+K0gIUJtOwj8
R1AejEP++cW90l6GgeJGdA8sdGVSY4QBIjqdPYeDNn/GitrTOe/E8H2d+54JmDwm
v3664219SXmJas/jbKPBXi3DXNVc5Y9ZIWwp4RruOGJvS+NHUXRMVIjMMrsaqUZQ
g4qnXYFJeIePGErHlUcVYYwHWee9Xlv1EqV6u4M5UaLXcyZqW8+VIm+02amypcsp
otLsrLMCxedX90M/FlgbkECgWe6ttBYhTwRuAaSszuO+ip4/NfFOayGU4kJWzfc=
=UFlT
-----END PGP SIGNATURE-----
next reply other threads:[~2009-05-06 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 16:53 Michael Raskin [this message]
2009-05-06 20:27 ` [MISFEATURE] Size reporting on small devices Michael Raskin
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=4A01C089.2080201@mail.ru \
--to=7c6f434c@mail.ru \
--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.