[stgt] can't force-remove targets

[Tomasz Chmielewski]

FUJITA Tomonori schrieb:

>> Which will output in syslog:
>>
>> May  6 17:05:35 superthecus tgtd: conn_close_force(230) close 3 0
>> May  6 17:05:35 superthecus tgtd: conn_close(89) already closed 0x9e5288c 4
>>
>>
>> And connection will not be removed.
> 
> I can't reproduce this when I do 'tgtadm --op update --mode sys --name State -v offl
> ine' before 'tgtadm --op delete --mode conn --tid 3 --sid 3 --cid 0'.

You mean it should prevent any initiator reconnections?
Yes, I use it as well, unfortunately, it (force-remove) doesn't always 
work for me; especially, when there is lots of IO (like dd).


Target 4: iqn.2007-02.net.syneticon:superthecus.test2
     System information:
         Driver: iscsi
         State: ready
     I_T nexus information:
         I_T nexus: 3
             Initiator: iqn.2006-12.net.syneticon:server.backup1
             Connection: 0
                 IP Address: 192.168.111.173

# tgtadm --op update --mode sys --name State -v offline
# tgtadm --op delete --mode conn --tid 4 --sid 3 --cid 0
# tgtadm --mode target --op delete --tid=4
tgtadm: this target unit is still active


After ~2 minutes the initiator will report IO error.

On the target, "netstat -tpna" shows no connection with the target.

Still though, "tgtadm --op show --mode target" shows the initiator as 
connected.

May  7 12:19:30 superthecus tgtd: conn_close_force(230) close 3 0
May  7 12:19:30 superthecus tgtd: conn_close(89) already closed 0x95fad84 1
May  7 12:19:30 superthecus tgtd: tgt_target_destroy(1739) target 4 
still has it nexus


Why does tgtd report "already closed"?


-- 
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html