public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org,
	Steven Pratt <slpratt@austin.ibm.com>,
	Eric Whitney <eric.whitney@hp.com>
Subject: ENOSPC patches integrated into the master branch
Date: Tue, 29 Sep 2009 14:42:38 -0400	[thread overview]
Message-ID: <20090929184238.GD7283@think> (raw)

Hello everyone,

A quick note that Josef's ENOSPC work is now integrated in the master
branch of the btrfs-unstable repo.  There is still a small window in his
accounting where ENOSPC oopsen can creep in, but the code is doing very
well here and the worst case estimates he uses are conservative enough
that I haven't been able to hit it yet.

My plan is to push this out for 2.6.32-rc2 and fine tune any performance
problems we find from there.  Josef is continuing to improve the code so
we'll have updates throughout the release cycle.

Eric and Steve, if you could both feed this into your respective torture
tests, it would be great.

ENOSPC gotchas:

btrfs-vol -b and device shrinking don't yet do all the checks required
for proper enospc support.  They do have some checks in place and most
of the time they will be fine, but we need to add more.

You probably won't hit 100% device utilization.  Btrfs splits up the
disk into metadata and data areas in relatively large chunks of about
1GB (sometimes more in multi-device setups).

This means you can end up with some space dedicated to metadata that
can't be used as data.

-chris


                 reply	other threads:[~2009-09-29 18:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090929184238.GD7283@think \
    --to=chris.mason@oracle.com \
    --cc=eric.whitney@hp.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=slpratt@austin.ibm.com \
    /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