All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Peter Geis <pgwipeout@gmail.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext4_xattr_ibody_find:2180: inode #2669312: comm systemd-journal: corrupted in-inode xattr
Date: Tue, 13 Jul 2021 17:43:10 +0200	[thread overview]
Message-ID: <20210713154310.GE24271@quack2.suse.cz> (raw)
In-Reply-To: <CAMdYzYqvT+X9C_YZ+DtspgHLSeb=RVHLeS2-0pEHeotyvb+iXQ@mail.gmail.com>

Hello!

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!

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

  reply	other threads:[~2021-07-13 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 12:36 ext4_xattr_ibody_find:2180: inode #2669312: comm systemd-journal: corrupted in-inode xattr Peter Geis
2021-07-13 15:43 ` Jan Kara [this message]
2021-07-13 20:52   ` Peter Geis
2021-07-14 17:56     ` Theodore Y. Ts'o

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=20210713154310.GE24271@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgwipeout@gmail.com \
    --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 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.