Dell H310, JBOD mode "hard error"

[Sean Bruno]

Not sure what to make of this.  I've tested a lot of svn revisions of
the thunderbolt code, but nothing looks obvious.  

When I use a single drive in "SYSPD" mode on a Dell H310 (falcon or
skinny drake) I get a /dev/mfisyspd0 device.  The JBOD mode *seems* to
work just fine as long as I don't do multiple things at once to it, e.g.
single user fsck works, but multiuser things die.

I get a failure case that emits errors such as:

g_vfs_done():error 27 in callback
mfisyspd0p2[READ(offset=7176192, length=425984)]mfisyspd0: hard error
error = 5
cmd=read 15360-16383
error 27 in callback
g_vfs_done():mfisyspd0: hard error mfisyspd0p2[READ(offset=7602176,
length=524288)]cmd=read error = 5
16384-17407
error 27 in callback
g_vfs_done():mfisyspd0: hard error mfisyspd0p2[READ(offset=8126464,
length=524288)]cmd=read error = 5
14560-15359
error 27 in callback
g_vfs_done():mfisyspd0: hard error mfisyspd0p2[READ(offset=7192576,
length=409600)]cmd=read error = 5
15360-16383


Sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freebsd.org/pipermail/freebsd-scsi/attachments/20130714/0ce98e86/attachment.sig>