On Feb 17, 2008 10:25 AM, Ross <[EMAIL PROTECTED]> wrote:
> 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.

Right, these aren't configurable - respective parameters are
hard-coded in iscsi/hdrs/iscsi.h:

    205 /*
    206  * NOP delay is used to send a iSCSI NOP (ie. ping) across the
    207  * wire to see if the target is still alive.  NOPs are only
    208  * sent when the RX thread hasn't received anything for the
    209  * below amount of time.
    210  */
    211 #define ISCSI_DEFAULT_NOP_DELAY                 5 /* seconds */
    212 extern int      iscsi_nop_delay;
    213 /*
    214  * If we haven't received anything in a specified period of time
    215  * we will stop accepting IO via tran start.  This will enable
    216  * upper level drivers to see we might be having a problem and
    217  * in the case of scsi_vhci will start to route IO down a better
    218  * path.
    219  */
    220 #define ISCSI_DEFAULT_RX_WINDOW                 20 /* seconds */
    221 extern int      iscsi_rx_window;
    222 /*
    223  * If we haven't received anything in a specified period of time
    224  * we will stop accepting IO via tran start.  This the max limit
    225  * when encountered we will start returning a fatal error.
    226  */
    227 #define ISCSI_DEFAULT_RX_MAX_WINDOW             180 /* seconds */
    228 extern int      iscsi_rx_max_window;


-- 
Regards,
Andrey

>
> 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
>
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to