public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.7
Date: Mon, 22 Jan 2024 20:16:03 +0100	[thread overview]
Message-ID: <20240122191605.6399-1-dsterba@suse.com> (raw)

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

                 reply	other threads:[~2024-01-22 19:16 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=20240122191605.6399-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox