From: "Stephen E. Baker" <baker.stephen.e@gmail.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>,
amstan@chromium.org, "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression
Date: Sat, 4 Jun 2022 23:21:46 -0400 [thread overview]
Message-ID: <CAFDdnB0uH_KqpN12pE2pyfb-vh_6Uab8Xdcb=NzQQy8ATEL+gA@mail.gmail.com> (raw)
In-Reply-To: <CAFDdnB143WXo2sz5trAhh2nH=CJ50U3GgkgDe_YJ394=G6ongg@mail.gmail.com>
On Sat, Jun 4, 2022 at 8:11 PM Stephen E. Baker
<baker.stephen.e@gmail.com> wrote:
>
> I reached out on the archlinuxarm IRC room and amstan offered the use
> of his device.
>
> When he boots my image he sees:
> "EXT4-fs (sda2): can't mount with superblock charset: utf8-12.1.0 not
> supported by the kernel. flags: 0x0."
At amstan's request I created a new root filesystem without casefold,
and created a loop device with casefold enabled. I am able to boot
with that filesystem.
zgrep UNICODE /proc/config
CONFIG_UNICODE=y
CONFIG_UNICODE_UTF8_DATA=y
CONFIG_UNICODE_NORMALIZATION_SELFTEST=m
mount /dev/loop0p1 /mnt
[ 679.358591] EXT-fs (loop0p1): can't mount with superblock charset:
utf8-12.1.0 not supported by the kernel. flags: 0x0
mount: /mnt: wrong fs type, bad option, bad superblock on
/dev/loop0p1, missing codepage or helper program, or other error.
So it seems I can produce the same error after boot that we saw in
early boot, which makes debugging much easier.
Given that is there anything I should be trying / looking for?
next prev parent reply other threads:[~2022-06-05 3:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 22:55 simplify ext4_sb_read_encoding regression Stephen E. Baker
2022-05-30 14:21 ` Gabriel Krisman Bertazi
2022-05-30 22:27 ` Stephen E. Baker
2022-05-31 0:56 ` Dave Chinner
2022-05-31 2:39 ` Stephen E. Baker
2022-06-02 17:47 ` Gabriel Krisman Bertazi
2022-06-05 0:11 ` Stephen E. Baker
2022-06-05 3:21 ` Stephen E. Baker [this message]
2022-06-05 6:23 ` Gabriel Krisman Bertazi
2022-06-05 13:56 ` Stephen E. Baker
[not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29 1:24 ` Theodore Ts'o
2022-05-29 12:19 ` Theodore Ts'o
2022-05-29 22:49 ` Stephen E. Baker
2022-05-30 1:49 ` Theodore Ts'o
2022-05-30 22:20 ` Stephen E. Baker
2022-05-31 0:16 ` Theodore Ts'o
2022-05-31 1:37 ` Theodore Ts'o
2022-06-02 2:06 ` Stephen E. Baker
2022-06-02 14:47 ` Theodore Ts'o
2023-04-14 23:01 ` William McVicker
2023-04-16 5:47 ` Christoph Hellwig
2023-04-16 5:56 ` Christoph Hellwig
2023-04-17 3:26 ` Theodore Ts'o
2023-04-17 16:16 ` Will McVicker
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='CAFDdnB0uH_KqpN12pE2pyfb-vh_6Uab8Xdcb=NzQQy8ATEL+gA@mail.gmail.com' \
--to=baker.stephen.e@gmail.com \
--cc=amstan@chromium.org \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 NNTP newsgroup(s).