From: Arne R. <arn...@go...> - 2011-05-27 18:47:21
|
2011/5/27 George Shuklin <geo...@gm...>: > On 27.05.2011 22:10, Arne Redlich wrote: >> >> 2011/5/27 Arne Redlich<arn...@go...>: >>> >>> 2011/5/27 Ross S. W. Walker<RW...@me...>: >>>> >>>> George Shuklin [mailto:geo...@gm...] wrote: >>>>> >>>>> I found ietadm rejects to delete target if it has active sessions. >>>>> Target was created dynamically, so I do really expected to be >>>>> allowed to say something like --op delete --force or --drop-sessions. >>>>> >>>>> Right now I know single way to delete targets will >>>>> established sessions from inititators - to reload ietd by >>>>> init.d script. But this kills every dynamically created >>>>> target, so its not really good idea for product enviroment... >>> >>> ietadm --op delete --tid=[id] --sid=[sid] --cid=[cid] >>> should do the trick - you can get id, sid and cid from >>> /proc/net/iet/session. >>> It's documented in the ietadm --help output and the ietadm manpage. > > Thanks, I'll try it. > >> Oh yes, you should make sure that the initiator doesn't reconnect, >> e.g. by placing a temporary iptables rule that blocks port 3260. > > Oops, that's a problem - I have over 50 initiators to single target with > their intension to reconnect to my target at any cost. And banning whole > iscsi via iptables is not better than /etc/init.d/iscsitarget stop... 50 initiators on the target you want to remove, or over all targets presented by iet? I guess the latter. Anyway, you could block the source ip? |