[stgt] can't force-remove targets

Tomasz Chmielewski mangoo at wpkg.org
Wed May 6 17:09:40 CEST 2009


Tomasz Chmielewski schrieb:
> Tomasz Chmielewski schrieb:
>> Sometimes (90% of cases), I can't force-remove targets (needed i.e. 
>> when I want to update tgtd).

The easiest way to reproduce is to:

- start a target
- on initiator, log in and "dd if=/dev/sdX of=/dev/null"
- on the target, try to remove this connection

Most likely, with a target like this:

Target 3: iqn.2007-02.net.syneticon:superthecus.test
     System information:
         Driver: iscsi
         State: ready
     I_T nexus information:
         I_T nexus: 3
             Initiator: iqn.2008-01.net.syneticon:server.vmware5
             Connection: 0
                 IP Address: 192.168.111.170


You will use this command to remove the connection:

# tgtadm --op delete --mode conn --tid 3 --sid 3 --cid 0


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.


-- 
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



More information about the stgt mailing list