From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 111381] mvsas 0.8.16 on Marvell 88SE9485 reports timeouts on load
Date: Mon, 08 Feb 2016 17:24:58 +0000 [thread overview]
Message-ID: <bug-111381-11613-t2UaehqXX4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111381-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111381
--- Comment #4 from Gabriel A. Devenyi <gdevenyi@gmail.com> ---
After much more research and reading, I believe I've found the root issue
causing the communication timeouts to the disks. I have not changed any cables
(other than reseating everything).
I came across several reports of marvell (mvsas) controllers randomly causing
issues with load, which mentioned SMART.
http://www.spinics.net/lists/linux-ide/msg50075.html
https://bugzilla.kernel.org/show_bug.cgi?id=42679
So I decided to stop smartd and try my load tests.
I have now gone through three iterations of high-load zfs scrubs along with
iotest.sh hammering the array simultaneously with no timeouts or communications
issues. I believe this indicates some issue with the driver/controller/disks
handling smart commands during load.
Do you have any recommendations as how I can test this further? Is there any
debug info I can provide?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-02-08 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:56 [Bug 111381] New: mvsas 0.8.16 on Marvell 88SE9485 reports timeouts on load bugzilla-daemon
2016-01-27 22:02 ` James Bottomley
2016-01-27 22:18 ` [Bug 111381] " bugzilla-daemon
2016-01-28 0:37 ` bugzilla-daemon
2016-01-28 0:47 ` James Bottomley
2016-02-05 16:33 ` bugzilla-daemon
2016-02-08 17:24 ` bugzilla-daemon [this message]
2016-02-09 0:11 ` [Bug 111381] mvsas 0.8.16 on Marvell 88SE9485 reports timeouts on load with SMART commands bugzilla-daemon
2016-04-01 18:56 ` 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-111381-11613-t2UaehqXX4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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.