FS#67936 - [e2fsprogs] too much escapes in e2fsck error message

Attached to Project: Arch Linux
Opened by Erich Eckner (deepthought) - Saturday, 19 September 2020, 09:45 GMT
Last edited by freswa (frederik) - Monday, 21 September 2020, 00:21 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

My latest run of e2fsck yields a lot of the following error messages (de_DE.UTF-8 locale):
"Block %$b von Inode %$i steht in Konflikt mit kritischen Metadaten, Blockprüfungen werden übersprungen."
This is of little help, as I do not see *which* inode and *which* block are bogus.

Additional info:
* package version(s)
e2fsprogs 1.45.6-2
glibc 2.32-4

Steps to reproduce:
Run e2fsck with LANG=de_DE.UTF-8 on a badly broken filesystem.

P.S.: I'm currently re-running with LC_ALL="C" to see, whether the problem persists for english locales, too, but e2fsck did not hit the bad inodes yet. I'll add a comment, when it does.
This task depends upon

Closed by  freswa (frederik)
Monday, 21 September 2020, 00:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  e2fsprogs 1.45.6-3
Comment by Erich Eckner (deepthought) - Saturday, 19 September 2020, 11:14 GMT
With LC_ALL="C" it shows useful information:
"Inode 732978821 block 2142765059 conflicts with critical metadata, skipping block checks."
Comment by loqs (loqs) - Saturday, 19 September 2020, 13:35 GMT
I thought that issue was already fixed by [1].

[1] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=aa773f808379cd0167281217bdcd7f3d87ae3201
Comment by Erich Eckner (deepthought) - Saturday, 19 September 2020, 18:55 GMT
yes, that looks, like it fixes a very similar issue - note, that I see "%$b" and not "%2$b". Maybe some future commit reintroduced the error?
Comment by Christian Hesse (eworm) - Saturday, 19 September 2020, 19:56 GMT
Please check if e2fsprogs 1.45.6-3 fixes this for you.
Comment by Erich Eckner (deepthought) - Sunday, 20 September 2020, 19:05 GMT
Yes, e2fsprogs 1.45.6-3 (from [testing], currently) works:

Block 110103398 von Inode 732980688 steht in Konflikt mit kritischen Metadaten, Blockprüfungen werden übersprungen.

Thanks!

Loading...