Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@redhat.com>
To: Lee Trager <lt73@cs.drexel.edu>
Cc: Josef Bacik <jbacik@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs thinks its full
Date: Thu, 20 Nov 2008 06:54:39 -0500	[thread overview]
Message-ID: <20081120115439.GH16041@unused.rdu.redhat.com> (raw)
In-Reply-To: <4924FBB3.6030101@cs.drexel.edu>

On Thu, Nov 20, 2008 at 12:54:59AM -0500, Lee Trager wrote:
> 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.
>

ENOSPC is kind of tricky, which is why it hasn't been done yet ;).  Since btrfs
does delayed allocation you are going to have to keep track of how much data we
want to allocate within this transaction so we don't run out of space while
we're doing the delalloc stuff.  Since btrfs is COW you also can't let the
amount of space you are going to alloc grow to the absolute largest it can for
the disk, since we are going to need space to COW the metadata blocks, so you
are going to have to keep a certain amount of space reserved so that you have
enough space to handle all the COW blocks that will be made.  It may be a bit
much for a first time project, I'd recommend hopping on the IRC channel and get
something to do from Chris, right now he's focusing on finalizing the disk
format, so there is alot of simple work to be done that will familiarize you
with some of the inner workings of btrfs.  When we get the disk layout finalized
I plan to tackle proper ENOSPC handling.  Thanks,

Josef 

      reply	other threads:[~2008-11-20 11: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
2008-11-20 11:54     ` Josef Bacik [this message]

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=20081120115439.GH16041@unused.rdu.redhat.com \
    --to=jbacik@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lt73@cs.drexel.edu \
    /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