From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs v0.15 released
Date: Thu, 29 May 2008 11:48:46 -0400 [thread overview]
Message-ID: <200805291148.46203.chris.mason@oracle.com> (raw)
Hello everyone,
Btrfs v0.15 is now available for download. The major feature added over v0.14
is the ability to remove devices online, and improved handling of IO failures
during reads and writes. v0.15 does not include any disk format changes over
v0.14.
You can find btrfs download information and documentation at:
http://btrfs.wiki.kernel.org/
Another highlight is the clone file data ioctl from Sage Weil, which can be
used to make a COW copy of a single file. btrfs-progs includes a new command
called bcp which can be used to run COW copies on single files or directory
trees.
Summary of fixes since v0.14
* 2.6.26-rc compile fixes (Mingming Cao)
* Fixes for IO stalls and high CPU usage during huge streaming writes (thanks
to Eric Whitney for testing these on 14TB files)
* Online device removal and degraded mounts
* Fixes to the online extent relocation and balancing code
* Deal with devices disappearing after initial btrfsctl -a scan
* Transparently correct IO errors on raid1 and raid10 by using the other
mirror.
* Detect misplaced btree writes by checking generation numbers during reads
* Fix nodatacow to more accurately detect snapshots
* Compile fixes for Apparmor kernels (Jeff Mahoney)
* Clone file data ioctl (Sage Weil)
* Fixes and optimizations for 2.6.18 enterprise kernels
-chris
next reply other threads:[~2008-05-29 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:48 Chris Mason [this message]
2008-06-02 23:42 ` 'cp -p' leaves mode on destination files/dirs incorrect Joe Peterson
2008-06-03 10:20 ` Yan Zheng
-- strict thread matches above, loose matches on Subject: below --
2008-05-29 15:45 Btrfs v0.15 released 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=200805291148.46203.chris.mason@oracle.com \
--to=chris.mason@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.