From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 89621] EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32
Date: Mon, 07 Feb 2022 09:34:40 +0000 [thread overview]
Message-ID: <bug-89621-13602-tyKhQSxl4N@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89621-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=89621
--- Comment #21 from GSI (kernel.org-115@groovy-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.
prev parent reply other threads:[~2022-02-07 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 12:28 [Bug 89621] New: EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32 bugzilla-daemon
2014-12-13 3:36 ` [Bug 89621] " bugzilla-daemon
2014-12-15 11:57 ` bugzilla-daemon
2014-12-15 14:51 ` bugzilla-daemon
2014-12-15 15:21 ` bugzilla-daemon
2014-12-15 22:27 ` bugzilla-daemon
2014-12-16 11:46 ` bugzilla-daemon
2014-12-16 14:55 ` bugzilla-daemon
2015-05-21 19:01 ` bugzilla-daemon
2015-05-27 9:53 ` bugzilla-daemon
2015-05-27 10:01 ` bugzilla-daemon
2015-05-28 0:27 ` bugzilla-daemon
2015-05-28 1:22 ` bugzilla-daemon
2015-05-28 5:24 ` bugzilla-daemon
2015-05-28 10:35 ` bugzilla-daemon
2015-07-24 16:17 ` bugzilla-daemon
2015-08-11 15:15 ` bugzilla-daemon
2015-08-11 18:16 ` bugzilla-daemon
2015-08-11 21:11 ` bugzilla-daemon
2015-08-12 9:08 ` bugzilla-daemon
2015-08-12 9:12 ` bugzilla-daemon
2022-02-04 13:13 ` bugzilla-daemon
2022-02-07 9:34 ` bugzilla-daemon [this message]
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-89621-13602-tyKhQSxl4N@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 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.