Thanks for the reply.

On 2月2日, 上午2时48分, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> Did you notice that when you run
> # iscsiadm -m node -r 68a68a -l
>
> and iscsiadm hangs, does iscsid die? It looks like the kernel detects a
> error, tries to tell userspace about it, but iscsid has died. Because
> iscsid is no longer up, iscsiadm will not be notified that the session
> was logged into, and will just sit around waiting for an answer.
>
> >  connection2:0: iscsi: detected conn error (1006)
After I ran the command iscsiadm, I thought the corresponding iscsid
didn't die, it seems sleep there. Even when I killed the iscsiadm, it
will still be there.

===========Logs================
# iscsiadm -m session
[02:68a68a] 45.246.0.251:3260,12545 iqn.1987-05.com.cisco:
05.eng246139.03-02.5006016339a03078
[01:69e9bd] 45.246.0.247:3260,12549 iqn.1987-05.com.cisco:
05.eng246139.03-06.5006016b39a03069
[00:694fbd] 45.246.0.247:3260,12549 iqn.1987-05.com.cisco:
05.eng246139.03-06.5006016339a03069
# ps -ef|grep iscsid
root      5727     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5728     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5881  5728  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17039  5728  0 05:13 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17869  5728  0 05:27 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     27908 16560  0 22:07 pts/2    00:00:00 grep iscsid
# iscsiadm -m node
[68a68a] 45.246.0.251:3260,12545 iqn.1987-05.com.cisco:
05.eng246139.03-02.5006016339a03078
[68028a] 45.246.0.251:3260,12545 iqn.1987-05.com.cisco:
05.eng246139.03-02.5006016a39a03078
[694fbd] 45.246.0.247:3260,12549 iqn.1987-05.com.cisco:
05.eng246139.03-06.5006016339a03069
[68a08a] 45.246.0.251:3260,12545 iqn.1987-05.com.cisco:
05.eng246139.03-02.5006016239a03078
[68008a] 45.246.0.251:3260,12545 iqn.1987-05.com.cisco:
05.eng246139.03-02.5006016b39a03078
[69e9bd] 45.246.0.247:3260,12549 iqn.1987-05.com.cisco:
05.eng246139.03-06.5006016b39a03069
# iscsiadm -m node -r 68028a -l
========Hung here=======
Another login:
# ps -ef|grep iscsid
root      5727     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5728     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5881  5728  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17039  5728  0 05:13 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17869  5728  0 05:27 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     27980 16560  0 22:08 pts/2    00:00:00 iscsiadm -m node -r
68028a -l
root     27989  5728  0 22:08 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid ( create the new process )
root     28339 17223  0 22:13 pts/4    00:00:00 grep iscsid
=====I kill iscsiadm=====
iscsiadm: caught SIGINT, exiting...
# ps -ef|grep iscsid
root      5727     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5728     1  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root      5881  5728  0 Jan29 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17039  5728  0 05:13 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     17869  5728  0 05:27 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid
root     27989  5728  0 22:08 ?        00:00:00 /sbin/iscsid -c /etc/
iscsid.conf -p /var/run/iscsi.pid ( Still here )
root     28350 17223  0 22:13 pts/4    00:00:00 grep iscsid
====================================================

>
> What version of open-iscsi tools is this (iscsiadm --version), and are
> you using the modules that come with suse's kernel? And what target are
> you using?

The open-iscsi tools is the original one come with the SuSE10 install
ISO, the version is 1.0-604.
And all the modules are come with suse.
The target is an EMC Clarrion ( and with a cisco MDS switch which I'm
not sure about ). But I don't think the target was the problem. I used
the same installation of SuSE10 on raw machine, it was no problem to
connect this target.

I was wondering if it's the problem of VMware virtual NIC driver. I
install the vmwareTools in this virtual machine.
# lsmod|grep vm
vmblock                18080  3
vmxnet                 18944  0
vmmemctl               14172  0
vmhgfs                 48896  0

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to