From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.6.1
Date: Sun, 5 Nov 2023 23:20:44 +0100 [thread overview]
Message-ID: <20231105222046.19483-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 6.6.1 have been released. This is an important bugfix release,
v6.6 is broken and should not be used.
Due to an accidental change in definition of the scanning ioctl in a
"documentation only" patch the mkfs or 'device scan' command were not able to
register all devices and mounting multi-device filesystems failed.
I misdiagnosed that as a change in the CI environment, thanks all early
packagers and testers for reports and the fix.
Changelog:
* fix device scanning ioctl definition, accidental change to the 'forget' ioctl
that breaks mounting multi-device filesystems
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.6.1
next reply other threads:[~2023-11-05 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 22:20 David Sterba [this message]
[not found] ` <aa605999-708c-4b8c-a05c-78fd2cc6b5b2@gmail.com>
2023-11-05 23:40 ` Btrfs progs release 6.6.1 Joe Salmeri
2023-11-09 14:38 ` David Sterba
2023-11-10 15:46 ` Joe Salmeri
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=20231105222046.19483-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