#1021927 Kernel 5.19 reports corrupted f2fs without corruption

Package:
src:linux
Source:
src:linux
Submitter:
Heinz Repp
Date:
2025-02-26 05:03:03 UTC
Severity:
normal
Tags:
#1021927#5
Date:
2022-10-17 12:26:15 UTC
From:
To:
Version: 5.19.6-1
Version: 5.19.11-1

Since 5.19, the kernel shows this error screen on every boot:

/dev/sdb4 is my root F2FS partition. The boot screen resembles the
dump.f2fs screen in the live system. I already ran fsck.f2fs /dev/sdb4
-a and -f from a GRML64 Debian testing based system (with kernel 
5.19.0-2) booted from an usb stick, but both reported no error (as does
the kernel, see above). I am using a fully updated Debian testing system.

The bug is merely annoying, as the system boots normally, but it is
annoying.
#1021927#14
Date:
2025-02-20 14:08:23 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore
#1021927#17
Date:
2025-02-20 14:08:23 UTC
From:
To:
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore
#1021927#24
Date:
2025-02-22 13:44:07 UTC
From:
To:
Since kernel 5.19.x this bug is present in all newer kernels, up to 6.12.12.
On every boot, it prints:

First, there is a reported corruption. But then, it says "No error was
reported". That's a little bit crazy. This came up with kernel 5.19,
without changing f2fs, but maybe this bug lives in f2fs?

Greetings

Heinz Repp
#1021927#29
Date:
2025-02-22 18:26:30 UTC
From:
To:
Hi Jaegeuk, hi Chao

We got the following report in Debian (cf.
https://bugs.debian.org/1021927) and quoted in the following:

Does this ring some bells to you?

Regards,
Salvatore
#1021927#36
Date:
2025-02-25 17:57:02 UTC
From:
To:
Hi

I do realize the subject was badly choosed so replying again with a
better subject. The downstream Debian report can be found at
https://bugs.debian.org/1021927

Does this ring some bell?

Regards,
Salvatore
#1021927#41
Date:
2025-02-26 02:13:40 UTC
From:
To:
Please don't worry, fsck has checked your device and reported that "Info: No
error was reported", it means there is no inconsistent problem in your image.

Eric has uploaded a patch to replace the unclear message "Info: Fix the reported
corruption." w/ "Info: Automatic fix mode enabled." [1], I guess we will see
the change in f2fs-tools 1.17.0+.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=84a218572118382f73997c6411ff80c98d3f6f94

Thanks,
#1021927#46
Date:
2025-02-26 05:01:25 UTC
From:
To:
Control: reassign -1 src:f2fs-tools 1.15.0-1
Control: tags -1 + upstream
Control: retitle -1 fsck.f2fs: use clearer info message for -a option
Hi,

Thanks a lot for the confirmation!

Regards,
Salvatore