From: Neal Gompa <neal@gompa.dev>
To: Linux BTRFS Development <linux-btrfs@vger.kernel.org>
Cc: Neal Gompa <neal@gompa.dev>, Anand Jain <anand.jain@oracle.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
David Sterba <dsterba@suse.cz>, Hector Martin <marcan@marcan.st>,
Sven Peter <sven@svenpeter.dev>,
Davide Cavalca <davide@cavalca.name>, Jens Axboe <axboe@fb.com>,
Asahi Lina <lina@asahilina.net>,
Asahi Linux <asahi@lists.linux.dev>
Subject: [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs
Date: Thu, 16 Nov 2023 11:02:23 -0500 [thread overview]
Message-ID: <20231116160235.2708131-1-neal@gompa.dev> (raw)
The Fedora Asahi SIG[0] is working on bringing up support for
Apple Silicon Macintosh computers through the Fedora Asahi Remix[1].
Apple Silicon Macs are unusual in that they currently require 16k
page sizes, which means that the current default for mkfs.btrfs(8)
makes a filesystem that is unreadable on x86 PCs and most other ARM
PCs.
This is now even more of a problem within Apple Silicon Macs as it is now
possible to nest 4K Fedora Linux VMs on 16K Fedora Asahi Remix machines to
enable performant x86 emulation[2] and the host storage needs to be compatible
for both environments.
Thus, I'd like to see us finally make the switchover to 4k sectorsize
for new filesystems by default, regardless of page size.
The initial test run by Hector Martin[3] at request of Qu Wenruo
looked promising[4], and we've been running with this behavior on
Fedora Linux since Fedora Linux 36 (at around 6.2) with no issues.
=== Changelog ===
v4: Fixed minor errors in the cover letter and patch subject
v3: Refreshed cover letter, rebased to latest, updated doc references for v6.7
v2: Rebased to latest, updated doc references for v6.6
Final v1: Collected Reviewed-by tags for inclusion.
RFC v2: Addressed documentation feedback
RFC v1: Initial submission
[0]: https://fedoraproject.org/wiki/SIGs/Asahi
[1]: https://fedora-asahi-remix.org/
[2]: https://sinrega.org/2023-10-06-using-microvms-for-gaming-on-fedora-asahi/
[3]: https://lore.kernel.org/linux-btrfs/fdffeecd-964f-0c69-f869-eb9ceca20263@suse.com/T/#m11d7939de96c43b3a7cdabc7c568d8bcafc7ca83
[4]: https://lore.kernel.org/linux-btrfs/fdffeecd-964f-0c69-f869-eb9ceca20263@suse.com/T/#mf382b78a8122b0cb82147a536c85b6a9098a2895
Neal Gompa (1):
btrfs-progs: mkfs: Enforce 4k sectorsize by default
Documentation/Subpage.rst | 15 ++++++++-------
Documentation/mkfs.btrfs.rst | 13 +++++++++----
mkfs/main.c | 2 +-
3 files changed, 18 insertions(+), 12 deletions(-)
--
2.39.2
next reply other threads:[~2023-11-16 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:02 Neal Gompa [this message]
2023-11-16 16:02 ` [PATCH v4 1/1] btrfs-progs: mkfs: Enforce 4k sectorsize by default Neal Gompa
2023-11-17 10:41 ` Eric Curtin
2023-11-27 16:07 ` [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs Josef Bacik
2023-11-28 15:01 ` Hector Martin
2023-11-28 19:57 ` Qu Wenruo
2023-11-28 20:09 ` Roman Mamedov
2023-11-28 20:31 ` Qu Wenruo
2023-11-28 21:24 ` Neal Gompa
2023-11-29 12:58 ` Hector Martin
2023-11-29 20:27 ` Qu Wenruo
2023-11-30 3:38 ` Neal Gompa
2023-12-13 22:25 ` David Sterba
2024-01-05 23:10 ` Neal Gompa
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=20231116160235.2708131-1-neal@gompa.dev \
--to=neal@gompa.dev \
--cc=anand.jain@oracle.com \
--cc=asahi@lists.linux.dev \
--cc=axboe@fb.com \
--cc=davide@cavalca.name \
--cc=dsterba@suse.cz \
--cc=lina@asahilina.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=quwenruo.btrfs@gmx.com \
--cc=sven@svenpeter.dev \
--cc=wqu@suse.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).