From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs release 3.18
Date: Tue, 30 Dec 2014 17:34:39 +0100 [thread overview]
Message-ID: <20141230163439.GP6490@suse.cz> (raw)
Hi,
let me announce the release of btrfs-progs version 3.18. There are
updates to UI and several enhancements of check/repair. About 100
commits from 14 contributors, thank you all!
Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
Major user-visible changes:
* mkfs - skinny-metadata feature is now on by default, first introduced
in kernel 3.10
New subcommands:
* filesystem usage - give an overview of fs usage in a way that's more
comprehensible than existing 'fi df'
* on kernels < 3.18: requires root due to restricted ioctl FS_INFO
* raid 5/6 numbers may be missing due to restricte ioctl (TREE_SEARCH)
* that's used to calculate the numbers
* device usage - more detailed information about per-device allocations
* same restrictions as for 'fi usage'
New features, options:
* check
* option to set a different tree root byte number
* ability to link lost files to lost+found, caused by a recent
kernel bug
* repair of severely corrupted fs (use with care):
* recover from corrupted b-tree
* ability to rebuild inode items from other items
* improved rebuilding of extent tree with snapshots
* convert
* option to show progress
* subvol create - print the commit mode inline, print the global mode
only if --verbose
Other updates:
* musl-libc build support
* bugfixes for coverity reports
* new test images, testing framework
* documentation
next reply other threads:[~2014-12-30 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 16:34 David Sterba [this message]
2014-12-30 17:25 ` Btrfs progs release 3.18 Martin Steigerwald
-- strict thread matches above, loose matches on Subject: below --
2014-12-30 21:38 Tomasz Chmielewski
2014-12-30 21:44 ` Hugo Mills
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=20141230163439.GP6490@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.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 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).