https://bugzilla.kernel.org/show_bug.cgi?id=89621 GSI (kernel.org-115@xxxxxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel.org-115@groovy-skill | |s.com --- Comment #20 from GSI (kernel.org-115@xxxxxxxxxxxxxxxxx) --- 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.
