https://bugzilla.kernel.org/show_bug.cgi?id=85751
Jaden changed:
What|Removed |Added
CC||jaden1...@gmail.com
--- Comment #4 from Jaden --
https://bugzilla.kernel.org/show_bug.cgi?id=85751
--- Comment #3 from Bart Van Assche ---
On 10/07/14 19:03, Mike Christie wrote:
> On 10/07/2014 11:42 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
>> * iscsiadm -m discovery -p 192.168.1.124 -t st
>> * iscsiadm -m node -p 192.168.1.124 -l
>> (so
On 10/07/14 19:03, Mike Christie wrote:
On 10/07/2014 11:42 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
* 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)
Did this login com
On 10/07/2014 11:42 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
> * 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)
Did this login command ever complete normally? Did you
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Bart Van Assche changed:
What|Removed |Added
Attachment #152781|Output generated by echo w |Output generated by echo w
descr
https://bugzilla.kernel.org/show_bug.cgi?id=85751
--- Comment #2 from Bart Van Assche ---
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
* is
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Bart Van Assche changed:
What|Removed |Added
Summary|iSCSI initiator lockup |iSCSI initiator lockup
7 matches
Mail list logo