On Tuesday, August 8, 2017 at 7:55:41 AM UTC-7, Frank Ritsema wrote:
> During changes in the iscsi SAN layout the initiator got confused, holding 
> on to a session in RAM while this session should not exists. 
> "iscsiadm -m session" shows 1 session. Trying to delete the record for it 
> fails because the session is in use
> The sessions persists, no matter what I try, even if all nodes, ifaces, 
> portals etc are deleted from the persistent DB. The only place there is a 
> reference to the session is in sysfs, which i cannot delete.

 The session information is kept in the initiator code in the kernel

> Trying to log it out with the daemon running fails because the session 
> keeps trying to log in to a target with wrong credentials (which i for some 
> reason cannot adjust with --op=update and node.session.auth.* variables; no 
> error, they just don't get saved)
> Trying to log out of the session with the daemon off returns a 'no records 
> found'.
> Every time the daemon starts it sees the device in sysfs and happily 
> starts trying to connect.

I am somewhat confused by your use of the term "sees the device in sysfs".

> As far as I am aware there is no way to force delete a broken session, 
> besides by rebooting. This is something I prefer not to do though.
> Is there something I'm missing?

What distro and versions are you running? This sounds like a kernel bug, 
which may have been fixed.

Can you reproduce this? 

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to