`<div dir="ltr">This *looks* like its SAS drives, but can you confirm that you're using SAS disks and not SATA drives in an expander or converter?<div><br></div><div>In particular, *really* bad things can happen when you use SATA drives with SAS expanders, particularly when you start encountering errors. These solutions work great when everything is working well, but they have catastrophic failure modes owing to cascading resets and timeouts, as SATA drives generally aren't individually reset, but rather the entire bus gets reset. Pure SAS should be fine though -- the HBAs will reset a single drive in the case of most SAS failure conditions, and these resets should not affect any other drives on the bus.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 2:20 PM, Eric Sproul <span dir="ltr"><<a href="mailto:esproul@omniti.com" target="_blank">esproul@omniti.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Dec 9, 2013 at 4:45 PM, Paul B. Henson <<a href="mailto:henson@acm.org">henson@acm.org</a>> wrote:<br>
<br>
> I vaguely recall seeing some mpt_sas improvements flyby over the past 6-8<br>
> months, once the first update for 151008 comes out I guess I will go ahead<br>
> and upgrade to that, maybe next time things go wiggy it won't take out the<br>
> whole controller.<br>
<br>
</div>We back-ported the major one, which was the fix for<br>
<a href="https://www.illumos.org/issues/4013" target="_blank">https://www.illumos.org/issues/4013</a> aka "backout 6910752/6968206:<br>
needs more work". Make sure you have<br>
driver/storage/mpt_sas@0.5.11,5.11-0.151006:20130906T160306Z which<br>
contains the fix.<br>
<div class="im"><br>
><br>
> One question; in this case, when it completely died, it ended up printing<br>
> out the wwn of the drive in question so it was easy to find. However, I'm<br>
> not quite sure how to map "target 17" to an actual disk if all I had were<br>
> the warning messages. Any pointers?<br>
<br>
</div>AFAIK mapping the topology behind an mpt_sas device required private<br>
ioctls to extract that info from the IOC. Josh Clulow did the grunt<br>
work to get that done, in <a href="https://www.illumos.org/issues/4018" target="_blank">https://www.illumos.org/issues/4018</a> and we<br>
have *that* stuff in r151008.<br>
<br>
In r151006 you would need to use LSI's "sas2ircu" utility to get that<br>
information.<br>
<span class="HOEnZb"><font color="#888888"><br>
Eric<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
-------------------------------------------<br>
illumos-discuss<br>
Archives: <a href="https://www.listbox.com/member/archive/182180/=now" target="_blank">https://www.listbox.com/member/archive/182180/=now</a><br>
RSS Feed: <a href="https://www.listbox.com/member/archive/rss/182180/22003744-9012f59c" target="_blank">https://www.listbox.com/member/archive/rss/182180/22003744-9012f59c</a><br>
Modify Your Subscription: <a href="https://www.listbox.com/member/?member_id=22003744&id_secret=22003744-e9cd8436" target="_blank">https://www.listbox.com/member/?member_id=22003744&id_secret=22003744-e9cd8436</a><br>
Powered by Listbox: <a href="http://www.listbox.com" target="_blank">http://www.listbox.com</a><br>
</div></div></blockquote></div><br></div>
`