All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Stephen E. Baker" <baker.stephen.e@gmail.com>
Cc: adilger.kernel@dilger.ca, hch@lst.de, linux-ext4@vger.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression
Date: Sat, 28 May 2022 21:24:30 -0400	[thread overview]
Message-ID: <YpLLTkje/QUYPP9z@mit.edu> (raw)
In-Reply-To: <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>

On Sat, May 28, 2022 at 06:53:59PM -0400, Stephen E. Baker wrote:
> Hello,
> 
> I have a Samsung Chromebook Plus (rk3399-gru-kevin) which boots linux off
> an external ssd plugged into USB. The root filesystem is ext4 with unicode
> support, case folding is enabled only on some directories in my home
> directory.
> 
> Since 5.17 the system has been unbootable.

Can you boot using an older kernel and send me (a) the output of
dumpe2fs -h of your root file system, and (b) the output of running
dmesg immediately after the system is booted?

If you can capture the console output when trying to boot 5.17, that
would be helpful.  You may need to disable the graphical boot screen
depending on what distribution or how the bootloader is configured.
If you could to take a picture of the screen when it stops/hangs, that
would be helpful.

I don't see anything wrong with the commit, and I've tested booting
the root file system with casefold enabled, and it works just fine.
What I did was take the root_fs.img from kvm-xfstests[1], and did the
following:

% qemu-img convert -O raw test-appliance/root_fs.img /tmp/root_fs.raw
% tune2fs -O casefold /tmp/root_fs.raw
% qemu-img convert -f raw -O qcow2 /tmp/root_fs.raw /tmp/root_fs.img
% kvm-xfstests -I /tmp/root_fs.img shell

and 5.17 booted without any problems.

[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-quickstart.md

Once in the kvm environment:

root@kvm-xfstests:~# uname -a
Linux kvm-xfstests 5.17.0-xfstests #644 SMP PREEMPT Sat May 28 21:06:37 EDT 2022 x86_64 GNU/Linux

root@kvm-xfstests:~# dmesg | grep EXT4-fs
[    0.690089] EXT4-fs (vda): Using encoding defined by superblock: utf8-12.1.0 with flags 0x0
[    0.690161] EXT4-fs (vda): Using encoding defined by superblock: utf8-12.1.0 with flags 0x0
[    0.690592] EXT4-fs (vda): mounted filesystem without journal. Quota mode: none.
[    0.846407] EXT4-fs (vda): re-mounted. Quota mode: none.
[    1.144539] EXT4-fs (vdg): mounted filesystem with ordered data mode. Quota mode: no

root@kvm-xfstests:~# dumpe2fs -h /dev/vda 2>/dev/null | grep -i features
Filesystem features:      ext_attr resize_inode dir_index filetype extent 64bit flex_bg casefold sparse_super large_file huge_file dir_nlink extra_isize metadata_csum

root@kvm-xfstests:~# dumpe2fs -h /dev/vda 2>/dev/null | grep -i encoding
Character encoding:       utf8-12.1

I'm not sure what is going on with your system, but I can't reproduce
it on my end.

Regards,

						- Ted

       reply	other threads:[~2022-05-29  1:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29  1:24 ` Theodore Ts'o [this message]
2022-05-29 12:19   ` simplify ext4_sb_read_encoding regression 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
2022-05-28 22:55 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
2022-06-05  6:23           ` Gabriel Krisman Bertazi
2022-06-05 13:56             ` Stephen E. Baker

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=YpLLTkje/QUYPP9z@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=baker.stephen.e@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.