Hi all,
When creating a new target port in targetcli (/qla2xxx create 21:0x:...), and I
have nothing plugged-in to the port, the creation process takes quite some
time. After a few seconds, the kernel prints a message saying "Cable is
unplugged...". So far so good.
It seems that when the target is created, it comes up in the 'enabled' state,
regardless of me having set 'auto_enable_tpgt=false'. Running 'disable' from
targetcli seems to try to bring the link up again ("Performing ISP error
recovery" then "Cable is unplugged...") and the target remains in the enabled
state.
If I then add LUNs and ACLs to the target, everything appears OK, but plugging
the target port into an initiator gives odd behaviour. The initiator spends a
very long time scanning the target and eventually times out and finds no LUNs.
The only way to get the port working again is to save the configuration and
reboot the target server, which is very frustrating.
I'm using targetcli as found in Debian wheezy with kernel 3.8.0, though I have
had this problem for a little while now...
Cheers,
Chris
--
Chris Boot
bo...@bootc.net
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
