On 04/03/2014 03:42 AM, [email protected] wrote: > 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? >
New. iscsiadm just writes to the scan/rescan sysfs files so yeah probably stuck in the kernel. I am not seeing this problem. When you run the rescan command is the target still down? Have we logged back in yet? Could you run the following command when you hit the problem: dmesg -c; echo w >/proc/sysrq-trigger; dmesg -c >waiting-tasks.txt. It will dump the stack traces in /var/log/messages, so we can see where we are stuck in the iscsi/scsi scan code. > Logs: Just ask. We have plenty. > > open-iscsi version: 2.0.873 (from Debian) > What kernel version is 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
