[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bug-89621-13602-tyKhQSxl4N@https.bugzilla.kernel.org/>
Date: Mon, 07 Feb 2022 09:34:40 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 89621] EXT4-fs error (device dm-1):
ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32
https://bugzilla.kernel.org/show_bug.cgi?id=89621
--- Comment #21 from GSI (kernel.org-115@...ovy-skills.com) ---
"This" in my last comment referring to the following output, which I had been
omitting unintentionally:
kvm [12151]: vcpu0, guest rIP: 0xffffffff010410a8 disabled perfctr wrmsr: 0xc1
data 0xabcd
kvm [14901]: vcpu0, guest rIP: 0xffffffff010410a8 disabled perfctr wrmsr: 0xc1
data 0xabcd
blk_update_request: critical medium error, dev sda, sector 1736391592 op
0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Aborting journal on device sda4-8.
EXT4-fs error (device sda4): ext4_journal_check_start:83: comm worker: Detected
aborted journal
EXT4-fs (sda4): Remounting filesystem read-only
The first two lines may not be related, but at least some (all?) bug reports on
the topic mentioned the machine in question being used as hypervisor.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists