I'm using the Solaris iSCSI Initiator (iscsiadm), and I've checked all the
documentation I can find but can't see anything configurable. Searching
google, or the sun sites hasn't turned up anything either.
I'll check with the ZFS group, but I suspect ZFS will simply rely on the
relevant disk driver to return the error codes. Otherwise they'll have to
second guess what is or isn't suitable for all the different possible protocols.
> iSCSI has built-in 'ping' implemented with
> NOP-{IN/OUT} protocol
> messages. This heartbeat is initiator-driven, so you
> should check
> whether this is configurable with iSCSI initiator you
> use and choose
> appropriate setting.
>
> Second part of the equation, namely how frequently
> zfs checks for pool
> disks health (in the absence of in-flight I/O to
> signal disk down with
> EIO), belongs to zfs-discuss.
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
