From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 85751] iSCSI initiator lockup during logout
Date: Tue, 07 Oct 2014 16:42:02 +0000 [thread overview]
Message-ID: <bug-85751-11613-AIXQdLQp7t@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85751-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85751
--- Comment #2 from Bart Van Assche <bvanassche@acm.org> ---
This is not easy to reproduce and happened while testing a modification of
iSCSI target software. The following commands were issued at the initiator
side:
* iscsiadm -m discovery -p 192.168.1.124 -t st
* iscsiadm -m node -p 192.168.1.124 -l
(something went wrong at the target side and the iSCSI initiator tried to
relogin)
* iscsiadm -m node -p 192.168.1.124 -u
Even after I powered off the virtual machine that was running the iSCSI target
software that last logout command did not finish. The system load raised to a
high value due to several kernel threads at the initiator side that got stuck
in an uninterruptible wait. It is only after the logout command had been issued
that I ran "echo w > /proc/sysrq-trigger".
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-10-07 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:08 [Bug 85751] New: iSCSI initiator lockup during login bugzilla-daemon
2014-10-07 15:49 ` [Bug 85751] " bugzilla-daemon
2014-10-07 16:34 ` [Bug 85751] iSCSI initiator lockup during logout bugzilla-daemon
2014-10-07 16:42 ` bugzilla-daemon [this message]
2014-10-07 17:03 ` Mike Christie
2014-10-07 18:29 ` Bart Van Assche
2014-10-07 16:42 ` bugzilla-daemon
2014-10-07 18:34 ` bugzilla-daemon
2016-10-27 13:21 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-85751-11613-AIXQdLQp7t@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.