Chris Mason wrote:
On Thu, Jun 04, 2009 at 02:02:20PM -0500, Steven Pratt wrote:
Chris Mason wrote:
Hello everyone,
Yan Zheng has been doing some major surgery to the back references and
extent allocation code, tackling bottlenecks in the code that tracks
extents. It scales better with many snapshots and performs better in
the common case of no snapshots at all.
THE NEW CODE IS A FORWARD ROLLING DISK FORMAT CHANGE. This means it is
compatible with the current btrfs disk format, but once you mount a
filesystem with the new code, it WILL NO LONGER BE MOUNTABLE FROM OLD
KERNELS. Old kernels spit out an error message when you try them on new
format filesystems.
This is a large change, and I'm hoping to have it stable in time for the
2.6.31 merge window. I've been testing it for about a week now, and
haven't been able to cause major problems yet. But, testing the
compatibility with old format filesystems is the hard part, and
everyone that pulls the new code should backup their data first.
I've setup git branches called newformat where you can pull the new code.
For the kernel (based on 2.6.30-rc7):
git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git newformat
So I started the performance runs on this. The base tests completed fine
on the raid system and I will post results as soon as I can finish
postprocessing, but when I tried to do nodatacow that machine it crashed
pretty early. Here is console log:
Thanks Steve. Just to clarify, which commit was the head of your git
tree when you ran these tests?
Commit: e84a00105718b4979e7fd8ae089e539168317728
Tree: fe8f97183bc849451837bcae612a398184ffa354
Parent: ca4ec9c2ba713999c9446f6f1bdcea092ffc8e12
Author: Chris Mason <chris.mason@xxxxxxxxxx> Mon, 18 May 2009 10:41:58 -0400
Committer: Chris Mason <chris.mason@xxxxxxxxxx> Wed, 03 Jun 2009 09:19:04 -0400
Btrfs: fix metadata dirty throttling limits
Steve
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
