From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Btrfs v0.14 Released
Date: Tue, 29 Apr 2008 16:01:32 -0400 [thread overview]
Message-ID: <200804291601.32945.chris.mason@oracle.com> (raw)
Hello everyone,
Btrfs v0.14 is now available for download. Please note the disk format has
changed, and it is not compatible with older versions of Btrfs.
For downloads and documention, please see the Btrfs project page:
http://btrfs.wiki.kernel.org
The oss.oracle.com Btrfs project page will soon start redirecting here.
v0.14 has a few performance fixes and closes some races that could have
allowed corrupted metadata in v0.13. The major new feature is the ability to
manage multiple devices under a single Btrfs mount. Raid0, raid1 and raid10
are supported.
Even for single device filesystems, metadata is now duplicated by default.
Checksums are verified after reads finish and duplicate copies are used if the
checksums don't match.
Multi-device design details can be found here:
http://btrfs.wiki.kernel.org/index.php/Multiple_Device_Support
And sample usage to create and add volumes can be found here:
http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
I'm putting up some benchmarks of the new multi-device code as the runs
finish:
http://btrfs.wiki.kernel.org/index.php/Multi-device_Benchmarks
Next up on the Btrfs todo list is finishing off the device removal and IO
error handling code. After that I'll add more fine grained locking to the
btrees.
Thanks to everyone who has helped contribute to and test this release.
-chris
next reply other threads:[~2008-04-29 20:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:01 Chris Mason [this message]
2008-05-01 16:04 ` Btrfs v0.14 Released Chris Mason
2008-05-01 16:18 ` Jeff Schroeder
2008-05-01 16:26 ` Chris Mason
2008-05-01 16:39 ` Jeff Schroeder
2008-05-01 19:06 ` Tim Gardner
2008-05-01 19:17 ` Chris Mason
2008-05-01 19:27 ` Jeff Mahoney
2008-05-01 19:36 ` Tim Gardner
2008-05-01 19:51 ` Kees Cook
2008-05-01 20:10 ` Jeff Mahoney
2008-05-02 6:40 ` Jan Engelhardt
2008-05-02 12:52 ` Chris Mason
2008-05-02 13:30 ` Jan Engelhardt
2008-05-02 14:10 ` Jan Engelhardt
2008-05-02 14:15 ` Jeff Schroeder
2008-05-02 14:31 ` Jan Engelhardt
2008-05-02 14:34 ` Chris Mason
2008-05-02 14:38 ` Matthew Wilcox
2008-05-02 14:52 ` Chris Mason
2008-05-02 15:07 ` Jan Engelhardt
2008-05-02 16:06 ` Tim Gardner
2008-05-02 16:26 ` Jeff Mahoney
2008-05-02 18:00 ` Jan Engelhardt
2008-05-02 18:01 ` Jeff Mahoney
2008-05-02 18:14 ` Jeff Schroeder
2008-05-02 20:58 ` 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=200804291601.32945.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).