From: Arne Jansen <sensille@gmx.net>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Li Zefan <lizf@cn.fujitsu.com>, Miao Xie <miaox@cn.fujitsu.com>,
slyfox@gentoo.org
Subject: Re: Integration branch pushed out to btrfs-unstable
Date: Wed, 25 May 2011 14:35:43 +0200 [thread overview]
Message-ID: <4DDCF79F.80405@gmx.net> (raw)
In-Reply-To: <1306179381-sup-443@shiny>
On 23.05.2011 21:54, Chris Mason wrote:
> Hi everyone,
>
> I've pushed out my current kernel git tree to a new branch called
> integration-test. This is meant for integration testing only and should
> not be run by anyone who doesn't love crashes.
>
> I've pulled together a lot of important work from a lot of different
> people. It includes:
>
> The new inode number allocator
> Delayed inode and directory item updates
> Scrub, chunk allocator fixes
> Races in device addition and removal
> Josef's performance fixes
> A large series of cleanups and fixes
>
> Most of the integration work was just pushing the cleanups into the new
> code bits. I still want to integrate Hugo Mills' balance progress
> ioctls (really nice). But it was a lot of work to get this all working
> together and I wanted to let everyone retest the result.
>
The commit
commit c4f675cd40d955d539180506c09515c90169b15b
Author: Sergei Trofimovich <slyfox@gentoo.org>
Date: Fri May 20 20:20:30 2011 +0000
btrfs: don't spin in shrink_delalloc if there is nothing to free
gives me very early ENOSPC in my tests on a small volume (7GB).
-Arne
next prev parent reply other threads:[~2011-05-25 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:54 Integration branch pushed out to btrfs-unstable Chris Mason
2011-05-24 9:01 ` Arne Jansen
2011-05-24 9:50 ` Li Zefan
2011-05-25 12:35 ` Arne Jansen [this message]
2011-05-25 18:44 ` Sergei Trofimovich
2011-05-25 20:41 ` Sergei Trofimovich
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=4DDCF79F.80405@gmx.net \
--to=sensille@gmx.net \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=miaox@cn.fujitsu.com \
--cc=slyfox@gentoo.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).