From: Dmitri Nikulin <dnikulin@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Entirely unexpected ENOSPC?
Date: Sun, 8 Mar 2009 19:35:44 +1100 [thread overview]
Message-ID: <3a7f57190903080035lf10104fq87eca697cc4dfb43@mail.gmail.com> (raw)
In-Reply-To: <2c259a8f0903072332n31d9d20dscad1801b4b468520@mail.gmail.com>
2009/3/8 Yien Zheng <esprout@gmail.com>:
> On Wed, 04 Mar 2009 14:48:43 -0600, Hugo Mills <hugo-lkml@carfax.org.uk> wrote:
> I just started playing with btrfs on my SSD drive last week and
> encountered the out of space problem using VirtualBox .vdi disks on
> the btrfs partition.
This is just a hunch, but maybe the handling of spare files (such as
.vdi) is not ideal or not what we're used to with extN. Normally
"skipped" blocks do not count towards the disk full size, but given
btrfs' nature they may count as a reservation that would certainly
cause an early ENOSPC.
You can try to narrow down the problem using qemu-img or dd. Example:
qemu-img create -f raw test.img 16G
See if it counts towards the disk fill count and ENOSPC threshold. See
if it even completes at all :P
--
Dmitri Nikulin
Centre for Synchrotron Science
Monash University
Victoria 3800, Australia
next prev parent reply other threads:[~2009-03-08 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 7:32 Entirely unexpected ENOSPC? Yien Zheng
2009-03-08 7:36 ` Yien Zheng
2009-03-08 8:35 ` Dmitri Nikulin [this message]
2009-03-09 13:08 ` Yien Zheng
2009-03-09 13:20 ` Hugo Mills
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 18:06 Hugo Mills
2009-03-04 18:50 ` Josef Bacik
2009-03-04 20:48 ` Hugo Mills
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=3a7f57190903080035lf10104fq87eca697cc4dfb43@mail.gmail.com \
--to=dnikulin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox