linux-ext4 - [Bug 202809] ext4: ext4_xattr_ibody_get:591: 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 for Android: free password hash cracker in your pocket

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

Message-ID: <bug-202809-13602-oscyagpMLH@https.bugzilla.kernel.org/>
Date: Fri, 13 Sep 2024 08:27:55 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 202809] ext4: ext4_xattr_ibody_get:591: comm systemd-journal:
 corrupted in-inode xattr

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

Gerald Boyle (peanutsunless@...il.com) changed:

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

--- Comment #6 from Gerald Boyle (peanutsunless@...il.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.