<div dir="ltr">We're seeing something similar on the same gear (LSI/supermicro expanders, lsi controllers, sata drives). <div><br></div><div>We've tried standard hardware debugging (cable reseat/replacement, etc) and the problem in our case seems to follow the sas expander backplane. </div>
<div><br></div><div>We did a disk by disk migration into a different expander and they stopped. </div><div><br></div><div>How high are your error counts? (in our case, we were getting about 1500/day/device). Is your performance impacted? (it was in our case)</div>
<div> -nld</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 13, 2013 at 10:20 AM, <span dir="ltr"><<a href="mailto:steve@linuxsuite.org" target="_blank">steve@linuxsuite.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Howdy!<br>
<br>
This is a SuperMicro JBOD with SATA disks. I am aware of the<br>
issues of having<br>
SATA on SAS, but was wondering just how serious these kinds of errors<br>
are.. a scrub of the pool<br>
completes without noticable problems.. I did a lot of stress testing<br>
earlier and could<br>
not get a failure. Disabling NCQ on the controller was a neccessary.<br>
What is the practical risk to data??<br>
<br>
See below info for iostat / syslog<br>
<br>
thanx - steve<br>
<br>
syslog info<br>
<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 scsi: [ID 243001 kern.warning]<br>
WARNING: /pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 #011mptsas_handle_event_sync:<br>
IOCStatus=0x8000, IOCLogInfo=0x31120303<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 scsi: [ID 243001 kern.warning]<br>
WARNING: /pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 #011mptsas_handle_event_sync:<br>
IOCStatus=0x8000, IOCLogInfo=0x31120436<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 scsi: [ID 243001 kern.warning]<br>
WARNING: /pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 #011mptsas_handle_event:<br>
IOCStatus=0x8000, IOCLogInfo=0x31120303<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 scsi: [ID 243001 kern.warning]<br>
WARNING: /pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
<br>
Blah Blah...<br>
<br>
kern.warning<4>: Aug 13 10:39:10 dfs1 #011mptsas_handle_event:<br>
IOCStatus=0x8000, IOCLogInfo=0x31120436<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 scsi: [ID 365881 <a href="http://kern.info" target="_blank">kern.info</a>]<br>
/pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 #011Log info 0x31120303 received for<br>
target 13.<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 #011scsi_status=0x0, ioc_status=0x804b,<br>
scsi_state=0xc<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 scsi: [ID 365881 <a href="http://kern.info" target="_blank">kern.info</a>]<br>
/pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 #011Log info 0x31120303 received for<br>
target 13.<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 #011scsi_status=0x0, ioc_status=0x804b,<br>
scsi_state=0xc<br>
<a href="http://kern.info" target="_blank">kern.info</a><6>: Aug 13 10:39:11 dfs1 scsi: [ID 365881 <a href="http://kern.info" target="_blank">kern.info</a>]<br>
/pci@0,0/pci8086,340d@6/pci1000,3080@0 (mpt_sas0):<br>
<br>
Output of iostat -En<br>
<br>
Looks like "Hard Errors" and "No Device" correspond. What<br>
does "Transport Error" and "Recoverable" mean. I see no evidence<br>
of data corruption/loss, does ZFS deal/recover from these errors in a<br>
good/safe<br>
way?<br>
<br>
<br>
c5t5000C500489947A8d0 Soft Errors: 0 Hard Errors: 2 Transport Errors: 11<br>
Vendor: ATA Product: ST3000DM001-9YN1 Revision: CC4H Serial No: W1F0AAMA<br>
Size: 3000.59GB <3000592982016 bytes><br>
Media Error: 0 Device Not Ready: 0 No Device: 2 Recoverable: 0<br>
Illegal Request: 2 Predictive Failure Analysis: 0<br>
<br>
c5t5000C500525EB2B9d0 Soft Errors: 0 Hard Errors: 5 Transport Errors: 46<br>
Vendor: ATA Product: ST3000DM001-9YN1 Revision: CC4H Serial No: W1F0QM5H<br>
Size: 3000.59GB <3000592982016 bytes><br>
Media Error: 0 Device Not Ready: 0 No Device: 5 Recoverable: 0<br>
Illegal Request: 5 Predictive Failure Analysis: 0<br>
<br>
c5t5000C50045561CEAd0 Soft Errors: 0 Hard Errors: 1 Transport Errors: 7<br>
Vendor: ATA Product: ST3000DM001-9YN1 Revision: CC4H Serial No: W1F09G4Q<br>
Size: 3000.59GB <3000592982016 bytes><br>
Media Error: 0 Device Not Ready: 0 No Device: 1 Recoverable: 0<br>
Illegal Request: 1 Predictive Failure Analysis: 0<br>
<br>
<br>
<br>
_______________________________________________<br>
OmniOS-discuss mailing list<br>
<a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>
<a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a><br>
</blockquote></div><br></div>