From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.33
Date: Fri, 29 Jan 2010 12:35:25 -0500 [thread overview]
Message-ID: <20100129173525.GA2819@think> (raw)
Hello everyone,
The btrfs-unstable master branch has some updates:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
It will pull into either 2.6.32 or 2.6.33-git.
These are bug fixes, mostly around btrfs multi-device code and replacing
failed drives. It also includes a fix for the orphan cleanup fix in the
last pull, this version is much better.
Outside of fixes, this adds mount -o compress-force, which won't back
off compressing files when part of the file doesn't compress well.
Aneesh Kumar K.V (1) commits (+9/-4):
Btrfs: Use correct values when updating inode i_size on fallocate
Chris Mason (1) commits (+11/-2):
Btrfs: Add mount -o compress-force
Josef Bacik (4) commits (+15/-10):
Btrfs: do not mark the chunk as readonly if in degraded mode (+5/-0)
Btrfs: check total number of devices when removing missing (+2/-2)
Btrfs: check return value of open_bdev_exclusive properly (+2/-2)
Btrfs: run orphan cleanup on default fs root (+6/-6)
Miao Xie (1) commits (+0/-14):
Btrfs: remove tree_search() in extent_map.c
Yang Hongyang (1) commits (+1/-0):
Btrfs: fix a memory leak in btrfs_init_acl
Total: (8) commits
fs/btrfs/acl.c | 1 +
fs/btrfs/ctree.h | 1 +
fs/btrfs/disk-io.c | 6 ++++++
fs/btrfs/extent_map.c | 14 --------------
fs/btrfs/inode.c | 22 +++++++++++-----------
fs/btrfs/super.c | 9 ++++++++-
fs/btrfs/volumes.c | 13 +++++++++----
7 files changed, 36 insertions(+), 30 deletions(-)
next reply other threads:[~2010-01-29 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 17:35 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-05 1:59 [GIT PULL] Btrfs updates for 2.6.33 Chris Mason
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=20100129173525.GA2819@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).