`<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 22, 2014 at 4:02 PM, Saso Kiselkov <span dir="ltr"><<a href="mailto:skiselkov.ml@gmail.com" target="_blank">skiselkov.ml@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><div class="">
# sg_write_buffer -v --in=MegalodonES3-SAS-STD-0004.LOD \<br>
--length=1625600 --mode=5 /dev/rdsk/c9t5000C500578F774Bd0<br>
Write buffer cmd: 3b 05 00 00 00 00 18 ce 00 00<br>
ioctl(USCSICMD) failed with os_err (errno) = 22<br>
write buffer: pass through os error: Invalid argument<br>
Write buffer failed res=-1<br>
<br>
</div>The situation is the same regardless of which path I disable. At the<br>
point of the sg_write_buffer, I also get a single SCSI error logged by<br>
"iostat -E", so it's clear there's something wrong going on on the SCSI<br>
bus. I suspect it might have something to do with what you mentioned,<br>
but I'm just no SCSI guru to figure this out.<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Saso<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">Like I said I use Santools. However, David Lethe, the author of Santools, who was a great help to me in working through this, informed me that from Solaris sg_write_buffer should be set to --mode-7 and possibly even set --length to 16384. I have not tested this.<br>
<br></div><div class="gmail_extra">For me Santools has been well worth it's investment on every ZFS server I've deployed.<br><br></div><div class="gmail_extra">-Chip<br></div></div>
`