From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203247] jbd2 gets stuck at jbd2_journal_commit_transaction frequently
Date: Fri, 12 Apr 2019 19:33:56 +0000 [thread overview]
Message-ID: <bug-203247-13602-oo3EFiaPsa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203247-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203247
--- Comment #9 from pkb07815 (pankajcabs@gmail.com) ---
Here is the complete information about disk:
# /opt/MegaRAID/MegaCli/MegaCli64 -pdlist -aALL
Adapter #0
Enclosure Device ID: 252
Slot Number: 0
Drive's position: DiskGroup: 0, Span: 0, Arm: 0
Enclosure position: N/A
Device Id: 6
WWN: 5000C500A167B624
Sequence Number: 2
Media Error Count: 0
Other Error Count: 0
Predictive Failure Count: 0
Last Predictive Failure Event Seq Number: 0
PD Type: SAS
Raw Size: 558.911 GB [0x45dd2fb0 Sectors]
Non Coerced Size: 558.411 GB [0x45cd2fb0 Sectors]
Coerced Size: 558.406 GB [0x45cd0000 Sectors]
Sector Size: 0
Logical Sector Size: 0
Physical Sector Size: 0
Firmware state: Online, Spun Up
Commissioned Spare : No
Emergency Spare : No
Device Firmware Level: N003
Shield Counter: 0
Successful diagnostics completion on : N/A
SAS Address(0): 0x5000c500a167b625
SAS Address(1): 0x0
Connected Port Number: 0(path0)
Inquiry Data: SEAGATE ST600MM0088 N003W420R7PJ
FDE Capable: Not Capable
FDE Enable: Disable
Secured: Unsecured
Locked: Unlocked
Needs EKM Attention: No
Foreign State: None
Device Speed: Unknown
Link Speed: 6.0Gb/s
Media Type: Hard Disk Device
Drive: Not Certified
Drive Temperature :28C (82.40 F)
PI Eligibility: No
Drive is formatted for PI information: No
PI: No PI
Port-0 :
Port status: Active
Port's Linkspeed: 6.0Gb/s
Port-1 :
Port status: Active
Port's Linkspeed: Unknown
Drive has flagged a S.M.A.R.T alert : No
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-04-12 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 16:15 [Bug 203247] New: jbd2 gets stuck at jbd2_journal_commit_transaction frequently bugzilla-daemon
2019-04-10 16:25 ` [Bug 203247] " bugzilla-daemon
2019-04-10 16:26 ` bugzilla-daemon
2019-04-10 16:27 ` bugzilla-daemon
2019-04-10 16:50 ` bugzilla-daemon
2019-04-10 17:57 ` bugzilla-daemon
2019-04-10 18:01 ` bugzilla-daemon
2019-04-10 18:06 ` bugzilla-daemon
2019-04-10 18:21 ` bugzilla-daemon
2019-04-12 19:33 ` bugzilla-daemon [this message]
2019-04-15 17:15 ` bugzilla-daemon
2019-04-15 21:09 ` 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-203247-13602-oo3EFiaPsa@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;
as well as URLs for NNTP newsgroup(s).