Hi,

btrfs-progs version 5.11.1 have been released. This is a bugfix release.

Changelog:

  * properly format checksums when a mismatch is reported
  * check: fix false alert on tree block crossing 64K page boundary
  * convert:
    * refuse to convert filesystem with 'needs_recovery'
    * update documentation to require fsck before conversion
  * balance convert: fix raid56 warning when converting other profiles
  * fi resize: improved summary
  * other
    * build: fix checks and autoconf defines
    * fix symlink paths for CI support scripts
    * updated tests

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:

David Sterba (10):
      btrfs-progs: ci: fix symlink paths of helper scripts
      btrfs-progs: tests: extend mkfs/001 to look for warnings after mkfs
      btrfs-progs: mkfs: enumerate all supported checksum algorithms in help 
text
      btrfs-progs: convert: refuse to convert filesystem with 'needs_recovery' 
set
      btrfs-progs: tests: add crafted image to test needs_recovery
      btrfs-progs: docs: change wording about required fsck
      btrfs-progs: balance: fix raid56 warning for other profiles
      btrfs-progs: tests: verify that ext4 supports extra_isize
      btrfs-progs: update CHANGES for 5.11.1
      Btrfs progs v5.11.1

Dāvis Mosāns (1):
      btrfs-progs: fix checksum output for "checksum verify failed"

Heiko Becker (1):
      btrfs-progs: build: Use PKG_CONFIG instead of pkg-config

Jaak Ristioja (1):
      btrfs-progs: check: fix typos in code comment and 1 typo in warning

Pierre Labastie (3):
      btrfs-progs: tests: fix quoting of sudo helper in 
misc/046-seed-multi-mount
      btrfs-progs: build: fix the test for EXT4_EPOCH_MASK
      btrfs-progs: build: do not use AC_DEFINE twice for a FIEMAP define

Qu Wenruo (1):
      btrfs-progs: fix false alert on tree block crossing 64K page boundary

Sidong Yang (1):
      btrfs-progs: fi resize: make output more readable

Reply via email to