On Wed, 06 May 2009 17:09:40 +0200 Tomasz Chmielewski <mangoo@xxxxxxxx> wrote: > 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. 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'. -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
