public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
* Btrfs progs release 6.7
@ 2024-01-22 19:16 David Sterba
  0 siblings, 0 replies; only message in thread
From: David Sterba @ 2024-01-22 19:16 UTC (permalink / raw)
  To: linux-btrfs

Hi,

btrfs-progs version 6.7 have been released.

Please note the change to the "mkfs --sectorsize", it's 4K by default and
requires the subpage support, recommended lowest kernel is 6.1. It would work
on older kernels too but there could be fixes or functionality missing.

This is namely for hosts that use the same filesystem on architectures with
different page size. In practice x86_64 has 4K, ARM most often configured with
4K too but there are 64K setups and 16K on the Macs.

Changelog:

   * mkfs: make 4k sectorsize default, recommended minimum kernel for that is
     6.1 and requires subpage support on architectures with page size > 4k
   * subvolume create: return correct error code when a target already exists
   * tree-checker: dump tree block on error (btrfs-convert, ...)
   * scrub limit: fix reporting of a limit set while there's none
   * fi usage: fix reporting of unallocated data or raid56 profile without root
     privs due to lack of that information
   * convert:
      * align data block group lengths to 64K
      * fix conversion of a large filesystem when there are partial inode items
        present due to caching
   * other:
      * build fixes
      * updated documentation
      * new and 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
Release: https://github.com/kdave/btrfs-progs/releases/tag/v6.7

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-01-22 19:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-01-22 19:16 Btrfs progs release 6.7 David Sterba

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox