From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.6.1
Date: Thu, 7 May 2020 14:06:46 +0200 [thread overview]
Message-ID: <20200507120646.12602-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.6.1 have been released.
The hilight of this minor release is the warning about multiple block groups
profiles, printed by several commands:
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
WARNING: Data: single, raid1
And the summary of 'fi usage' prints:
Multiple profiles: yes (data)
This might need some fine tuning, or more to be put to documenation but
I think the current status is ok so let's get it out to get feedback
eventually.
Changelog:
* print warning when multiple block group profiles exist, update 'fi usage'
summary, add docs to maual page explaining the situation
* build: optional support for libgcrypt or libsodium, providing hash
implementations
* other:
* fixed, updated and new tests
* cleanups
* updated docs
No change since rc1.
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
Shortlog:
Alexandru Ungureanu (2):
btrfs-progs: docs: improved asciidoc syntax to fix rendering issues
btrfs-progs: docs: add example on deleting a subvolume
Anand Jain (1):
btrfs-progs: tests: drop trailing slash from TEST_TOP path
David Sterba (19):
btrfs-progs: remove obsolete fs_info::fs_mutex
btrfs-progs: move backref.[ch] to kernel-shared/
btrfs-progs: add more hash implementation providers
btrfs-progs: docs: clarify mount options
btrfs-progs: tests: enhance README
btrfs-progs: tests: add coverage for multiple profiles warning
btrfs-progs: remove unused function btrfs_check_for_mixed_profiles_by_path
btrfs-progs: rename helpers for multiple block group checks
btrfs-progs: unexport btrfs_get_string_for_multiple_profiles
btrfs-progs: simplify string dump of block group profiles
btrfs-progs: simplify string separator checks in sprint_profiles
btrfs-progs: reorder single to be first in multiple bg list
btrfs-progs: adjust multiple block group warning format
btrfs-progs: fix detection of multiple profiles when generating the strings
btrfs-progs: fi usage: list multiple profiles type
btrfs-progs: docs: update section about multiple block group profiles
btrfs-progs: tests: clean loop devices created by tests
btrfs-progs: update CHANGES for 5.6.1
Btrfs progs v5.6.1
Goffredo Baroncelli (5):
btrfs-progs: add code for checking mixed profile function
btrfs-progs: add mixed profiles check to some btrfs sub-commands.
btrfs-progs: fi usage: add check for multiple profiles
btrfs-progs: add further checks for multiple profiles
btrfs-progs: docs: add section about multiple profiles
Marcos Paulo de Souza (1):
btrfs-progs: tests: mkfs/018, fix check for truncate command failure
Qu Wenruo (6):
btrfs-progs: remove extent_buffer::tree member
btrfs-progs: do proper error handling in add_cache_extent()
btrfs-progs: fix bad kernel header non-flat include case
btrfs-progs: tests: filter output for run_check_stdout
btrfs-progs: tests: introduce expand_command() to inject aruguments more accurately
btrfs-progs: remove the duplicated @level parameter for btrfs_bin_search()
reply other threads:[~2020-05-07 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200507120646.12602-1-dsterba@suse.com \
--to=dsterba@suse.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.