public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Btrfs changes for 2.6.29-rc
Date: Thu, 19 Mar 2009 09:53:25 -0400	[thread overview]
Message-ID: <1237470805.18446.22.camel@think.oraclecorp.com> (raw)


Hello,

The master branch of:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git

Has two commits fixing problems with adding devices or growing devices
in a btrfs filesystem.  

Basically the code that actually allocates space wasn't being properly
told about the new space, and so the only way to make use of it was to
unmount and mount again.


Chris Mason (2):
      Btrfs: Fix locking around adding new space_info
      Btrfs: Clear space_info full when adding new devices

 
 fs/btrfs/ctree.h       |    9 +++++++++
 fs/btrfs/extent-tree.c |   45 ++++++++++++++++++++++++++++++++++++++++++---
 fs/btrfs/volumes.c     |    8 ++++++++
 3 files changed, 59 insertions(+), 3 deletions(-)


                 reply	other threads:[~2009-03-19 13:54 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=1237470805.18446.22.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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