public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 202809] ext4: ext4_xattr_ibody_get:591: comm systemd-journal: corrupted in-inode xattr
Date: Fri, 13 Sep 2024 08:27:55 +0000	[thread overview]
Message-ID: <bug-202809-13602-oscyagpMLH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202809-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202809

Gerald Boyle (peanutsunless@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peanutsunless@gmail.com

--- Comment #6 from Gerald Boyle (peanutsunless@gmail.com) ---
The error messages you're encountering indicate that there is filesystem
corruption on your EXT4 filesystem, particularly related to extended attributes
(xattrs). To run fsck safely, unmount the filesystem. If it's your root
filesystem, you may need to use a live CD/USB or boot into single-user 
mode.umount /dev/mmcblk1p1
fsck.ext4 -f -y /dev/mmcblk1p1
smartctl -a /dev/mmcblk1
Check system logs for additional context around the time the errors occur. Logs
like /var/log/syslog or /var/log/messages might provide more insights. I
noticed that a new driver is available at
http://www.ralinktech.com/ralink/Home/Support/Linux.html
https://geometrydashworld.net
Identify if there is a pattern or specific actions that correlate with the
corruption, which might help isolate the cause.  Persistent filesystem
corruption could indicate failing storage hardware. While eMMC storage is
generally reliable, it can still fail or degrade over time.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-09-13  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  8:39 [Bug 202809] New: ext4: ext4_xattr_ibody_get:591: comm systemd-journal: corrupted in-inode xattr bugzilla-daemon
2019-03-08  3:50 ` [Bug 202809] " bugzilla-daemon
2019-03-08 18:10 ` bugzilla-daemon
2019-03-09  7:43 ` bugzilla-daemon
2019-04-11  1:40 ` bugzilla-daemon
2021-01-18  2:33 ` bugzilla-daemon
2024-09-13  8:27 ` bugzilla-daemon [this message]
2024-09-13 20:32 ` bugzilla-daemon
2024-09-13 20:32 ` bugzilla-daemon

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=bug-202809-13602-oscyagpMLH@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox