linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>, Josef Bacik <josef@redhat.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: [PATCH V2 0/6] random bugfixes of the space management
Date: Wed, 29 Dec 2010 18:18:31 +0800	[thread overview]
Message-ID: <4D1B0AF7.1000907@cn.fujitsu.com> (raw)

Hello, Chris

I have a bunch of random fixes of the space management in

git://repo.or.cz/linux-btrfs-devel.git space-manage

They are the ENOSPC fixes, as well as fixes for df command.
The first one and the last one fixed the wrong free space information reported
by df command. The second one fixed ENOSPC when there is tiny space in the
filesystem. And The third fixed wrong calculation of stripe size. And the 4th
and 5th patches fixed the chunk allocation problem when the block devices have
no enough space to allocate a default-size chunk.

Changelog V1 -> V2:
- fix compiler errors on x86_32 machines.
- fix some bugs when allocating dup chunks.
- break the chunk allocation when errors happen.
- just allocate min_stripes stripes when the free space is not enough.
- cleanup redundant code

You can merge this patchset to your "next" branch directly after dropping
the top four patches of the "next" branch.

Thanks
Miao
---
 fs/btrfs/ctree.h       |    2 +
 fs/btrfs/extent-tree.c |   71 +++++-
 fs/btrfs/super.c       |  147 +++++++++++-
 fs/btrfs/volumes.c     |  615 +++++++++++++++++++++++++++++++++++-------------
 fs/btrfs/volumes.h     |   27 ++
 5 files changed, 686 insertions(+), 176 deletions(-)

             reply	other threads:[~2010-12-29 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 10:18 Miao Xie [this message]
2011-01-04  5:46 ` [PATCH V2 0/6] random bugfixes of the space management Mitch Harder
2011-01-04  6:42   ` Miao Xie
2011-01-05 10:13   ` Miao Xie

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=4D1B0AF7.1000907@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=josef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).