From: Roman Mamedov <rm@romanrm.net>
To: Qu Wenruo <wqu@suse.com>
Cc: Hector Martin <marcan@marcan.st>,
Josef Bacik <josef@toxicpanda.com>, Neal Gompa <neal@gompa.dev>,
Linux BTRFS Development <linux-btrfs@vger.kernel.org>,
Anand Jain <anand.jain@oracle.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
David Sterba <dsterba@suse.cz>, 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: Re: [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs
Date: Wed, 29 Nov 2023 01:09:13 +0500 [thread overview]
Message-ID: <20231129010913.295c0fa9@nvm> (raw)
In-Reply-To: <f229058e-4f5d-4bd0-9016-41b133688443@suse.com>
On Wed, 29 Nov 2023 06:27:26 +1030
Qu Wenruo <wqu@suse.com> wrote:
> > Reminder that the Raspberry Pi 5 is also shipping with 16K pages by
> > default now. The clock is ticking for an ever-growing stream of people
> > upset that they can't mount/data-rescue/etc their rPi5 NAS disks from an
> > x86 machine ;)
>
> As long as they are using 5.15+ kernel, they should be able to mount and
> use their RPI NAS with disks from x86 machines.
Doesn't the subpage sectorsize featureset only support sectors less than page
size, not the other way round?
"mkfs.btrfs -s 16K" fails to mount on 6.1.62:
[1077897.120376] BTRFS error (device dm-22): sectorsize 16384 not yet supported for page size 4096
[1077897.120624] BTRFS error (device dm-22): superblock contains fatal errors
[1077897.121394] BTRFS error (device dm-22): open_ctree failed
--
With respect,
Roman
next prev parent reply other threads:[~2023-11-28 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:02 [PATCH v4 0/1] Enforce 4k sectorize by default for mkfs Neal Gompa
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 [this message]
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=20231129010913.295c0fa9@nvm \
--to=rm@romanrm.net \
--cc=anand.jain@oracle.com \
--cc=asahi@lists.linux.dev \
--cc=axboe@fb.com \
--cc=davide@cavalca.name \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=lina@asahilina.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--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