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: Fri, 04 Feb 2022 13:13:50 +0000 [thread overview]
Message-ID: <bug-89621-13602-hp2LAAAyxY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89621-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=89621
GSI (kernel.org-115@groovy-skills.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kernel.org-115@groovy-skill
| |s.com
--- Comment #20 from GSI (kernel.org-115@groovy-skills.com) ---
This is on a HP ProLiant DL380 G7 with HP Smart Array P410 controller with 8
disks configured as RAID-6.
S.M.A.R.T. reports the disks as healthy.
The server has been running for roughly ten months before this issue occured
the 1st of this month.
fsck did some repairs. Two days later, 3rd, the issue occured again.
What is the meaning of the suffix -8 as reported by
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/tree/fs/jbd2/journal.c#n2422
for j_devname?
Regardless of actual device, all bug reports appear to have that -8 in common.
Examples:
"Aborting journal on device sda3-8."
https://askubuntu.com/questions/595024/suddenly-read-only-file-system-ext4
"Aborting journal on device dm-2-8."
https://bugzilla.kernel.org/show_bug.cgi?id=102731
"Aborting journal on device sda2:8."
https://bbs.archlinux.org/viewtopic.php?id=70077
"Aborting journal on device vda1-8."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672
"Aborting journal on device dm-1-8."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/comments/26
"Aborting journal on device dm-9-8."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672/comments/28
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-02-04 13:13 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 [this message]
2022-02-07 9:34 ` 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-89621-13602-hp2LAAAyxY@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;
as well as URLs for NNTP newsgroup(s).