[stgt] can't force-remove targets

[Tomasz Chmielewski]

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


tgtd is running 19 targets, mostly in use, on a 64 bit system.


These are tgtadm commands I use to remove the targets:


tgtadm --op update --mode sys --name State -v offline

# This target is removed just fine
tgtadm --op unbind --mode target --tid 11 -I ALL
tgtadm --op delete --mode conn --tid 11 --sid 14 --cid 0
tgtadm --mode target --op delete --tid=11

# This target is removed fine
tgtadm --mode target --op delete --tid=6

# This target fails
tgtadm --op delete --mode conn --tid 16 --sid 11 --cid 0
tgtadm --mode target --op delete --tid=16
tgtadm: this target unit is still active

(Command: tgtadm --mode target --op delete --tid=16
exited with code: 22.)





Any idea why this happens? Currently, with 0.9.6, but happened also at 
least with 0.9.4 and 0.9.5, and perhaps earlier.

Running "tgtadm --op delete --mode conn --tid 16 --sid 11 --cid 0" 
manually, multiple times later does not remove the connection.


Target 16: iqn.2009-04.net.syneticon:san3.sys14
     System information:
         Driver: iscsi
         State: offline
     I_T nexus information:
         I_T nexus: 11
             Initiator: iqn.2009-03.net.syneticon:server.sys14
             Connection: 0
                 IP Address: 192.168.112.74
     LUN information:
         LUN: 0
             Type: controller
             SCSI ID: IET     00100000
             SCSI SN: beaf160
             Size: 0 MB
             Online: Yes
             Removable media: No
             Backing store: No backing store
         LUN: 1
             Type: disk
             SCSI ID: IET     00100001
             SCSI SN: beaf161
             Size: 26844 MB
             Online: Yes
             Removable media: No
             Backing store: /dev/san3/sys14
     Account information:
     ACL information:


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