linux-ext4 - Re: ext4_xattr_ibody_find:2180: inode #2669312: comm systemd-journal: corrupted in-inode xattr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMdYzYroicgDkWuiQ7Xaw_5aYD9mLkrz8qvE9WwS6mPw9uWe8g@mail.gmail.com>
Date:   Tue, 13 Jul 2021 16:52:11 -0400
From:   Peter Geis <pgwipeout@...il.com>
To:     Jan Kara <jack@...e.cz>
Cc:     tytso@....edu, adilger.kernel@...ger.ca,
        linux-ext4@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: ext4_xattr_ibody_find:2180: inode #2669312: comm systemd-journal:
 corrupted in-inode xattr

On Tue, Jul 13, 2021 at 11:43 AM Jan Kara <jack@...e.cz> wrote:
>
> Hello!

Good Evening,

>
> On Fri 28-05-21 08:36:17, Peter Geis wrote:
> > I have run into a fun issue where I have the follow error on boot,
> > which causes the device to drop to read only mode:
> > ext4_xattr_ibody_find:2180: inode #2669312: comm systemd-journal:
> > corrupted in-inode xattr
> > It marks the file system as unclean, which forces a fsck, but it seems
> > that even as of v1.46.2 e2fsprogs does not have the ability to resolve
> > this issue.
> > Any attempts to touch the corrupted files (I've found two so far)
> > leads to the same error, and I cannot find a way to remove or repair
> > the affected inodes without wiping the entire file system.
>
> This seems to have fallen through the cracks. Have you managed to fix your
> filesystem? If not, please obtain filesystem image using e2image (it will
> contain only fs metadata, not any data), compress it and put it somewhere for
> download so that we can better diagnose the issue. Thanks!

Unfortunately no I don't have the file system anymore.
I put about two weeks into trying to fix it, but in the end I had to
nuke it from orbit.

Thanks for reaching out,
Peter

>
>                                                                 Honza
> --
> Jan Kara <jack@...e.com>
> SUSE Labs, CR