From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 202809] New: ext4: ext4_xattr_ibody_get:591: comm systemd-journal: corrupted in-inode xattr
Date: Thu, 07 Mar 2019 08:39:49 +0000 [thread overview]
Message-ID: <bug-202809-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=202809
Bug ID: 202809
Summary: ext4: ext4_xattr_ibody_get:591: comm systemd-journal:
corrupted in-inode xattr
Product: File System
Version: 2.5
Kernel Version: 4.19.23-19
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: feng.tang@intel.com
Regression: No
Created attachment 281569
--> https://bugzilla.kernel.org/attachment.cgi?id=281569&action=edit
fsck output
When we run some stress test on our platform, we saw error message like this:
[49074.700194] EXT4-fs error (device mmcblk1p1): ext4_xattr_ibody_get:591:
inode #164242: comm systemd-journal: corrupted in-inode xattr
[49074.701633] EXT4-fs error (device mmcblk1p1): ext4_xattr_ibody_get:591:
inode #164247: comm systemd-journal: corrupted in-inode xattr
[49074.703260] EXT4-fs error (device mmcblk1p1): ext4_xattr_ibody_get:591:
inode #164245: comm systemd-journal: corrupted in-inode xattr
[49079.621065] EXT4-fs error: 39 callbacks suppressed
kernel version is 4.19.23-19.
CPU: Intel(R) Atom(TM) Processor A3960 @ 1.90GHz
rootfs: emmc storage card
Running on top of a hypervisor (ACRN)
When the error message happens, the GUI will stop working, sometimes the serial
console will stop too, but we can still connect to it through SSH connections,
and if we run fsck on that system, will see some error info (full log
attached).
some are:
Multiply-claimed block(s) in inode 164223: 656535
Multiply-claimed block(s) in inode 164224: 673971 757260--758282
Multiply-claimed block(s) in inode 164225: 656531
File
/var/log/journal/cf5c3ff473bd4a2dbfc890565e0439f9/system@e2d41008f0ce4d53849cdc7cec0f8a29-000000000003045c-0005831a9bb56af7.journal
(inode #164224, mod time Sat Mar 2 11:13:48 2019)
has 1024 multiply-claimed block(s), shared with 1 file(s):
/var/log/crashlog/vmevent393_98cd58c91b1da34b635e/crashfile (inode
#164240, mod time Sat Mar 2 11:13:48 2019)
Could you please help to check, and provide some hints for debugging? thanks!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2019-03-07 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 8:39 bugzilla-daemon [this message]
2019-03-08 3:50 ` [Bug 202809] ext4: ext4_xattr_ibody_get:591: comm systemd-journal: corrupted in-inode xattr 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
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@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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