On Wed, 01 Mar 2006, Maxim Kozover wrote:
> Hi Andrew!
> I applied the patch changing 2 lines in scsi_transport_fc.c to
> if (fc_host_tgtid_bind_type(shost) != FC_TGTID_BIND_NONE) {
>
> I tried first with Emulex as QLogic seemed yesterday to have more
> problems, (not only orphan rports, but also not creating all rports),
> so let's start solving problems one by one.
>
> I saw no change in behavior with Emulex.
> 1. I had 3 LUNs on adapters 6 and 7.
> # ls /sys/class/fc_remote_ports
> rport-6:0-0 rport-6:0-1 rport-6:0-2 rport-7:0-0 rport-7:0-1 rport-7:0-2
Ok, so specifically you have one target-port at rport-7:0-2 which has
three luns (0, 1, and 2).
/devices/pci0000:00/0000:00:06.0/0000:05:00.2/0000:07:01.1/host7/rport-7:0-2/target7:0:0/7:0:0:0
/devices/pci0000:00/0000:00:06.0/0000:05:00.2/0000:07:01.1/host7/rport-7:0-2/target7:0:0/7:0:0:1
/devices/pci0000:00/0000:00:06.0/0000:05:00.2/0000:07:01.1/host7/rport-7:0-2/target7:0:0/7:0:0:2
So what are the other rports? Other initiators?
> 2. disconnected the cable between adapter 7 and the switch,
> rport-7:0-0 disappeared momentarily with Emulex LinkDown event.
> lpfc 0000:07:01.1: 1:1305 Link Down Event x2 received Data: x2 x20 x110
> # ls /sys/class/fc_remote_ports
> rport-6:0-0 rport-6:0-1 rport-6:0-2 rport-7:0-0 rport-7:0-2
Actually, rport-7:0-1 disappears -- my guess an initiator. Is
rport-7:0-0 an FCP_TARGET with no luns?
> 3. Then after a timeout I got a message about blocking rport-7:0-2, but
> nothing changed.
> rport-7:0-2: blocked FC remote port time out: removing target and saving binding
Exactly, the scsi_target and scsi_device is reaped after TMO expires.
> # ls /sys/class/fc_remote_ports
> rport-6:0-0 rport-6:0-1 rport-6:0-2 rport-7:0-0 rport-7:0-2
This is still correct.
> However, all scsi entries related to adapter 7 are removed from
> /proc/scsi/scsi.
>
> Please advise.
If your question is, are the /proc/scsi/scsi devices (/dev/sda, sdb,
...) supposed to disappear when the rport TMO expires , then yes they
are supposed to disappear. The rports persist with a port_state of
'not present' for persistent-binding purposes, until the port return
(i.e. you reinsert the cable). If that were to occur, then upon rport
addition, the 3-lun storage would be attached to rport-7:0-2 and a
request signaled for lun scanning by the midlayer.
--
Andrew
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
