Mike Christie wrote:
Do you mean the /dev/sdX's getting created or the kernel scsi scanning code
detecting luns?
I did not see either.
Mike, from this log you can see that the kernel scsi code detected the new scsi
host (98) / lun
on it and assigned the sdd device for that lun, but I can
Shyam,
-Original Message-
From: shyam_i...@dell.com [mailto:shyam_i...@dell.com]
Sent: Wednesday, December 22, 2010 9:23 PM
To: open-iscsi@googlegroups.com
Cc: Rustad, Mark D
Subject: RE: DCB support for iSCSI
-Original Message-
From: open-iscsi@googlegroups.com
Mike,
-Original Message-
From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com]
On Behalf Of Mike Christie
Sent: Tuesday, December 21, 2010 6:54 PM
To: open-iscsi@googlegroups.com
Cc: Rustad, Mark D
Subject: Re: DCB support for iSCSI
Does you guys know what is up
[...] you can see that the kernel scsi code detected the new scsi host (98) /
lun
on it and assigned the sdd device for that lun, but I can tell that this all
happens only @
16:07:18 which is seven seconds --after-- the lun was detected @ 16:07:11
If we both use the same .config is there
On Mon, 2010-12-20 at 18:36 -0600, Mike Christie wrote:
On 12/20/2010 03:30 AM, Nicholas A. Bellinger wrote:
After a quick audit of iscsi_session-lock usage, and I see that
iscsi_complete_pdu(), iscsi_tmf_timedout(), iscsi_eh_cmd_timed_out(),
iscsi_check_transport_timeouts() are using
