Hi, In a scenario where we reboot a remote target and then run "iscsiadm -m session --rescan" on the initiator, iscsiadm starts taking around 85% CPU, and any other iscsiadm command we send afterwards also gets stuck (probably waiting on a mutex), and the "rescan" iscsiadm process can't be killed (niether with kill -9 or -11), so it's probably stuck in the kernel.
Is this a known/fixed issue? Logs: Just ask. We have plenty. open-iscsi version: 2.0.873 (from Debian) Have a nice day :) -- 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 firstname.lastname@example.org. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.