From: Lee Trager <lt73@cs.drexel.edu>
To: Josef Bacik <jbacik@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs thinks its full
Date: Thu, 20 Nov 2008 00:54:59 -0500 [thread overview]
Message-ID: <4924FBB3.6030101@cs.drexel.edu> (raw)
In-Reply-To: <20081119222343.GF16041@unused.rdu.redhat.com>
Is that just finishing btrfs_check_free_space? What would that involve?
I haven't done much kernel work but I could give it a try.
Lee
Josef Bacik wrote:
> On Wed, Nov 19, 2008 at 05:24:34PM -0500, Lee Trager wrote:
>
>> Because the last bug I dealt with had so much to do with the disk being
>> full I decided to test and see what happens when I fill up the disk.
>> Unfortunatly the disk thinks its full before it actually is. I have a
>> 7539M btrfs partition and tried to fill it by doing
>>
>> dd if=/dev/zero of=/mnt/btrfs/fill
>>
>> btrfs reports its full after 6408M have been used. dd, ls, and df all
>> confirm this. This uses only 85% of the disk but I can not put one more
>> bit onto the partition. The only thing that shows up in my system logs
>> is "space info full 1." I am using the latest git sources.
>>
>>
>
> Yup thats by design :). Theres a 85% full short-circuit in there to keep the
> panic unpleasentness from happening since there isn't proper ENOSPC handling.
> This will be tossed when the ENOSPC handling is done. Thanks,
>
> Josef
>
next prev parent reply other threads:[~2008-11-20 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 22:24 btrfs thinks its full Lee Trager
2008-11-19 22:23 ` Josef Bacik
2008-11-20 5:54 ` Lee Trager [this message]
2008-11-20 11:54 ` Josef Bacik
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=4924FBB3.6030101@cs.drexel.edu \
--to=lt73@cs.drexel.edu \
--cc=jbacik@redhat.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 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.