Re: [PATCH 1/1] cxgb3i: Fix a login over vlan issue
Patrick McHardy wrote:
k...@chelsio.com wrote:
[PATCH 1/1] cxgb3i: Fix a login over vlan issue
From: Karen Xie k...@chelsio.com
Fix a login over vlan issue, when parent interface is vlan and we are using
cxgb3i sepecific private ip address in '/etc/iscsi/ifaces/' iface file.
+/**
+ * cxgb3i_find_dev - find the interface associated with the given address
+ * @ipaddr: ip address
+ */
+static struct net_device *cxgb3i_find_dev(__be32 ipaddr)
+{
+struct flowi fl;
+int err;
+struct rtable *rt;
+
+memset(fl, 0, sizeof(fl));
+fl.nl_u.ip4_u.daddr = ipaddr;
+
+err = ip_route_output_key(init_net, rt, fl);
+if (!err)
+return (rt-u.dst)-dev;
+
+return NULL;
+}
This probably shouldn't be using init_net but the current namespace.
Hi Patrick,
Thanks for review, will fix that and send another path shortly.
Regards
Rakesh Ranjan
signature.asc
Description: OpenPGP digital signature
RE: Need help with multipath and iscsi in CentOS 5.4
Hi Kyle. For your configuration do you have a LUN in the storage group assigned to your server? If so, the LUN is presented to both SPs (service processors) but only owned by one. If your storage group for the server has been configured for the default mode the LUN is presented in PNR mode; therefore, only one SP owns it and can be used for the IO. In order to use the LUN thru the other SP the LUN needs to be trespassed to that SP. If the storage group for the server is configured for ALUA mode then you can read and write thru both SPs without a trespass command. If there are no LUNs assigned in a storage group for your server, then the LUN that is presented to the server is a LUNZ and you will not be able to access it. You indicate below that you are able to fdisk one of the SCSI devices but not all four. If you are configured in the manner you described you should be able to access it thru the two NICs that attached to the SP that owns the LUN. Regards, Wayne. EMC Corp -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:52 PM To: open-iscsi@googlegroups.com Subject: Re: Need help with multipath and iscsi in CentOS 5.4 Kyle Schmitt wrote: I'm cross-posting here from linux-iscsi-users since I've seen no linux-scsi-users would be for centos 4. Centos 5 uses a different initiator, but you are the right place finally :) traffic in the weeks since I posted this. Hi, I needed a little help or advice with my setup. I'm trying to configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box. Very short version: One server with two NICs for iSCSI sees storage on EMC. Storage shows up as four discs, but only one works. So far single connections work: If I setup the box to use one NIC, I get one connection and can use it just fine. When I setup multiple connections I have problems... I created two interfaces, and assigned each one to a NIC iscsiadm -m iface -I iface0 --op=new iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth2 iscsiadm -m iface -I iface1 --op=new iscsiadm -m iface -I iface1 --op=update -n iface.net_ifacename -v eth3 Each interface saw two paths to their storage, four total, so far so good. I logged all four of them them in with: iscsiadm -m node -T long ugly string here -l I could see I was connected to all four via iscsiadm-m session At this point, I thought I was set, I had four new devices /dev/sdb /dev/sdc /dev/sdd /dev/sde Ignoring multipath at this point for now, here's where the problem started. I have all four devices, but I can only communicate through one of them: /dev/sdc. As a quick test I tried to fdisk all four partitions, to see if I saw the same thing in each place, and only /dev/sdc works. What do you mean by works? Can you dd it, or fdisk it? Turning on multipath, I got a multipathed device consisting of sdb sdc sdd and sde, but sdb sdd and sde are failed with a message of checker msg is emc_clariion_checker: Logical Unit is unbound or LUNZ Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Could you send the /var/log/messages for when you run the login command so I can see the disk info? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RE: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
Is CHAP configured on the array? -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:54 PM To: open-iscsi@googlegroups.com Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011) avora wrote: I do not see ping/nop timeout message in the logs (probably that's why changing the noop timeouts did not work). Simply starting the session does not cause these errors. On starting the second session, I start a daemon that does SCSI commands like INQUIRY on all the paths. After that I see these messages, and the daemon gets stuck for a very long time waiting for SCSI commands to finish. At the backend I have EMC CLARiiON. # iscsiadm -m node -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091100683.a2 Portal: 192.168.10.1:3260,1 Iface Name: iface0 Target: iqn.1992-04.com.emc:cx.ckm00091100683.b2 Portal: 192.168.12.1:3260,3 Iface Name: iface1 Does the same path always fail? If you log into one can you use it, then if you logout and log into the other does that other one then work? Is there any info the clarrion logs? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
Yes Mike, the recovery message is seen right away. Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after recovery (1 attempts) 'conn error' and 'recovery' are seen one after the other, continuosly. On Dec 10, 8:04 am, Mike Christie micha...@cs.wisc.edu wrote: avora wrote: I got a similar issue while browsing http://groups.google.com/group/open-iscsi/browse_thread/thread/3c9c37... I wanted to enable logging as mentioned in above link. echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_conn echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_session echo 1 /sys/module/libiscsi/parameters/debug_libiscsi_eh echo 1 /sys/module/iscsi_tcp/parameters/debug_iscsi_tcp echo 1 /sys/module/libiscsi_tcp/parameters/debug_libiscsi_tcp --- But on my machine I only see. # ls /sys/module/libiscsi/ refcnt sections srcversion # ls /sys/module/iscsi_tcp/ parameters refcnt sections srcversion # ls /sys/module/iscsi_tcp/parameters/max_lun /sys/module/iscsi_tcp/parameters/max_lun Your open-iscsi version is older and does not have those settings. # iscsiadm -m session -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091100683.a3 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FAILED Internal iscsid Session State: REPOEN You might be seeing something else. I did not get what exactly you meant Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after recovery (1 attempts) After theconnerrormessage do you see one of these right away? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
recognise new lun added
a client has login to a target. the target has added a new lun. how could the client recognises the new lun? i have tried iscsiadm -m discovery -t sendtargets without luck. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
specify which lun attached to which scsi disk
#iscsiadm -m session -P 3 Attached SCSI devices: Host Number: 5 State: running scsi5 Channel 00 Id 0 Lun: 0 scsi5 Channel 00 Id 0 Lun: 1 Attached scsi disk sdb State: running scsi5 Channel 00 Id 0 Lun: 2 Attached scsi disk sdc State: running pls advise if it is possible to specify which lun could be attached to which scsi disk instead of randomly assigned? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: [PATCH 1/5] BNX2I - Add 5771E device support to bnx2i driver
On Wed, 2009-12-09 at 20:45 -0600, Mike Christie wrote: Reviewed-by: Mike Christie micha...@cs.wisc.edu But not by checkpatch: ERROR: trailing whitespace #23: FILE: drivers/scsi/bnx2i/bnx2i_init.c:90: +^I^Iprintk(KERN_ALERT bnx2i: unknown device, 0x%x\n, $ total: 1 errors, 0 warnings, 13 lines checked I've fixed it up. And the several other whitespace problems in the rest of the patch set. James -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Need help with multipath and iscsi in CentOS 5.4
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote: Kyle Schmitt wrote: What do you mean by works? Can you dd it, or fdisk it? it works by most any measure sdc: I can dd it, fdisk it, mkfs.ext3 it, run iozone, etc. In contrast sdb sdd and sde cant be fdisked, dded, or even less -fed. Have you created a lun that is accessible to the initiator defined in /etc/iscsi/initiatorname.iscsi? Yup, I've got a lun, and can read/write to it. Could you send the /var/log/messages for when you run the login command so I can see the disk info? Sure, let me dig it out... it'll be a few minutes. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: [PATCH 1/5] BNX2I - Add 5771E device support to bnx2i driver
On Thu, 2009-12-10 at 07:43 -0800, James Bottomley wrote: On Wed, 2009-12-09 at 20:45 -0600, Mike Christie wrote: Reviewed-by: Mike Christie micha...@cs.wisc.edu But not by checkpatch: ERROR: trailing whitespace #23: FILE: drivers/scsi/bnx2i/bnx2i_init.c:90: +^I^Iprintk(KERN_ALERT bnx2i: unknown device, 0x%x\n, $ total: 1 errors, 0 warnings, 13 lines checked I've fixed it up. And the several other whitespace problems in the rest of the patch set. Thanks James. In future will make sure not to repeat the slip-up. Thanks again. James -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
[PATCH 1/1 v2] cxgb3i: Fix a login over vlan issue
[PATCH 1/1 v2] cxgb3i: Fix a login over vlan issue
From: Rakesh Ranjan rak...@chelsio.com
Fix a target login issue, when parent interface is vlan and we are using
cxgb3i sepecific private ip address in '/etc/iscsi/ifaces/' iface file.
Acked-by: Karen Xie k...@chelsio.com
Signed-off-by: Rakesh Ranjan rak...@chelsio.com
---
drivers/scsi/cxgb3i/cxgb3i_offload.c | 34 +-
1 files changed, 33 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/cxgb3i/cxgb3i_offload.c
b/drivers/scsi/cxgb3i/cxgb3i_offload.c
index 26ffdcd..15a00e8 100644
--- a/drivers/scsi/cxgb3i/cxgb3i_offload.c
+++ b/drivers/scsi/cxgb3i/cxgb3i_offload.c
@@ -1440,6 +1440,10 @@ void cxgb3i_c3cn_release(struct s3_conn *c3cn)
static int is_cxgb3_dev(struct net_device *dev)
{
struct cxgb3i_sdev_data *cdata;
+ struct net_device *ndev = dev;
+
+ if (dev-priv_flags IFF_802_1Q_VLAN)
+ ndev = vlan_dev_real_dev(dev);
write_lock(cdata_rwlock);
list_for_each_entry(cdata, cdata_list, list) {
@@ -1447,7 +1451,7 @@ static int is_cxgb3_dev(struct net_device *dev)
int i;
for (i = 0; i ports-nports; i++)
- if (dev == ports-lldevs[i]) {
+ if (ndev == ports-lldevs[i]) {
write_unlock(cdata_rwlock);
return 1;
}
@@ -1566,6 +1570,26 @@ out_err:
return -EINVAL;
}
+/**
+ * cxgb3i_find_dev - find the interface associated with the given address
+ * @ipaddr: ip address
+ */
+static struct net_device *
+cxgb3i_find_dev(struct net_device *dev, __be32 ipaddr)
+{
+ struct flowi fl;
+ int err;
+ struct rtable *rt;
+
+ memset(fl, 0, sizeof(fl));
+ fl.nl_u.ip4_u.daddr = ipaddr;
+
+ err = ip_route_output_key(dev ? dev_net(dev) : init_net, rt, fl);
+ if (!err)
+ return (rt-u.dst)-dev;
+
+ return NULL;
+}
/**
* cxgb3i_c3cn_connect - initiates an iscsi tcp connection to a given address
@@ -1581,6 +1605,7 @@ int cxgb3i_c3cn_connect(struct net_device *dev, struct
s3_conn *c3cn,
struct cxgb3i_sdev_data *cdata;
struct t3cdev *cdev;
__be32 sipv4;
+ struct net_device *dstdev;
int err;
c3cn_conn_debug(c3cn 0x%p, dev 0x%p.\n, c3cn, dev);
@@ -1591,6 +1616,13 @@ int cxgb3i_c3cn_connect(struct net_device *dev, struct
s3_conn *c3cn,
c3cn-daddr.sin_port = usin-sin_port;
c3cn-daddr.sin_addr.s_addr = usin-sin_addr.s_addr;
+ dstdev = cxgb3i_find_dev(dev, usin-sin_addr.s_addr);
+ if (!dstdev || !is_cxgb3_dev(dstdev))
+ return -ENETUNREACH;
+
+ if (dstdev-priv_flags IFF_802_1Q_VLAN)
+ dev = dstdev;
+
rt = find_route(dev, c3cn-saddr.sin_addr.s_addr,
c3cn-daddr.sin_addr.s_addr,
c3cn-saddr.sin_port,
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
Help: iface problems
Hi all, I got some problems when I set up iface. The initiator node has two NIC eth0 is eth1. I set up eth0 to connect the router by browsing Web. And eth1 will link to a disk array. In the default mode iscsi will log in the target machine by using eth0 so I wanna change into eth1. I followed steps by the doc Open-ISCSI provide. However, I doubt there are some mistakes the doc may have. In the file /etc/iscsi/iface0 I have added necessary information like iface.transport_name = tcp iface.hwaddress = XX:XX:XX:XX:XX:XX But it seems useless. Because when I use command iscsiadm -m iface That doesn't show the iface0 just default and iser. And One thing makes me confused, which file I REALLY need to set up iface? Because the Open-ISCSI doc mentioned /etc/iscsi/ifaceX this file, /etc/iscsi/ifaces file and even /etc/iscsi/ifaces/ifaceX this file. Obviously file names and folder names cannot be the same. But why it happen in this doc? So I hope someone could show me a correct steps to set up ifaces. My OS is Cent OS 5.4. Thank you very much. Best Regards, Eric -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
RE: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
There is no CHAP configured on the array. --- On Thu, 12/10/09, berthiaume_wa...@emc.com berthiaume_wa...@emc.com wrote: From: berthiaume_wa...@emc.com berthiaume_wa...@emc.com Subject: RE: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011) To: open-iscsi@googlegroups.com Date: Thursday, December 10, 2009, 7:29 AM Is CHAP configured on the array? -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf Of Mike Christie Sent: Wednesday, December 09, 2009 9:54 PM To: open-iscsi@googlegroups.com Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011) avora wrote: I do not see ping/nop timeout message in the logs (probably that's why changing the noop timeouts did not work). Simply starting the session does not cause these errors. On starting the second session, I start a daemon that does SCSI commands like INQUIRY on all the paths. After that I see these messages, and the daemon gets stuck for a very long time waiting for SCSI commands to finish. At the backend I have EMC CLARiiON. # iscsiadm -m node -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091100683.a2 Portal: 192.168.10.1:3260,1 Iface Name: iface0 Target: iqn.1992-04.com.emc:cx.ckm00091100683.b2 Portal: 192.168.12.1:3260,3 Iface Name: iface1 Does the same path always fail? If you log into one can you use it, then if you logout and log into the other does that other one then work? Is there any info the clarrion logs? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
avora wrote: Yes Mike, the recovery message is seen right away. Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after recovery (1 attempts) 'conn error' and 'recovery' are seen one after the other, continuosly. Do you have other initiators connected to the target? Can you get me a wireshark trace? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: specify which lun attached to which scsi disk
aclhkaclhk aclhkaclhk wrote: #iscsiadm -m session -P 3 Attached SCSI devices: Host Number: 5 State: running scsi5 Channel 00 Id 0 Lun: 0 scsi5 Channel 00 Id 0 Lun: 1 Attached scsi disk sdb State: running scsi5 Channel 00 Id 0 Lun: 2 Attached scsi disk sdc State: running pls advise if it is possible to specify which lun could be attached to which scsi disk instead of randomly assigned? It is random. Do not use names like sdx. Use the ones made in /dev/disk/. They are persistent. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: recognise new lun added
aclhkaclhk aclhkaclhk wrote: a client has login to a target. the target has added a new lun. how could the client recognises the new lun? iscsiadm -m session --rescan will rescan all sessions iscsiadm -m session -R sid --rescan will rescan the specific session with sid. iscsiadm -m node -T target --rescan will rescan sessions to that target. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Help: iface problems
Lee Amy wrote: Hi all, I got some problems when I set up iface. The initiator node has two NIC eth0 is eth1. I set up eth0 to connect the router by browsing Web. And eth1 will link to a disk array. In the default mode iscsi will log in the target machine by using eth0 so I wanna change into eth1. I followed steps by the doc Open-ISCSI provide. However, I doubt there are some mistakes the doc may have. In the file /etc/iscsi/iface0 I It should be in /etc/iscsi/ifaces have added necessary information like iface.transport_name = tcp iface.hwaddress = XX:XX:XX:XX:XX:XX But it seems useless. Because when I use command iscsiadm -m iface That doesn't show the iface0 just default and iser. And One thing makes me confused, which file I REALLY need to set up iface? Because the Open-ISCSI doc mentioned /etc/iscsi/ifaceX this This should be fixed in newer docs. Use iscsiadm in iface mode. It will take care of these types of issues for you in the future. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
I did sent the ethereal trace yesterday. I am not sure why it didn't reach, is there any place I can upload it ? There is only 1 initiator. # iscsiadm -m session -P 1 Target: iqn.1992-04.com.emc:cx.ckm00091100683.a3 Current Portal: 192.168.11.1:3260,2 Persistent Portal: 192.168.11.1:3260,2 ** Interface: ** Iface Name: iface0 Iface Transport: tcp Iface Initiatorname: iqn.1996-04.de.suse:02:9914ca52960 Iface IPaddress: 192.168.11.11 Iface HWaddress: 00:15:17:A8:A9:1E Iface Netdev: eth0 SID: 10 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FAILED Internal iscsid Session State: REPOEN Target: iqn.1992-04.com.emc:cx.ckm00091100683.b3 Current Portal: 192.168.13.1:3260,4 Persistent Portal: 192.168.13.1:3260,4 ** Interface: ** Iface Name: iface1 Iface Transport: tcp Iface Initiatorname: iqn.1996-04.de.suse:02:9914ca52960 Iface IPaddress: 192.168.13.11 Iface HWaddress: 00:15:17:A8:A9:1F Iface Netdev: eth1 SID: 11 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FAILED Internal iscsid Session State: REPOEN --- On Thu, 12/10/09, Mike Christie micha...@cs.wisc.edu wrote: From: Mike Christie micha...@cs.wisc.edu Subject: Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011) To: open-iscsi@googlegroups.com Date: Thursday, December 10, 2009, 11:22 PM avora wrote: Yes Mike, the recovery message is seen right away. Dec 7 18:42:06 cdc-r710s1 iscsid: connection2:0 is operational after recovery (1 attempts) 'conn error' and 'recovery' are seen one after the other, continuosly. Do you have other initiators connected to the target? Can you get me a wireshark trace? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)
Anuarg Vora wrote: I did sent the ethereal trace yesterday. I am not sure why it didn't reach, is there any place I can upload it ? http://groups-beta.google.com/group/open-iscsi/files -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
where is Dimitry and Alex (guys that manage open-iscsi.org)
Hey, Dimitry or Alex, do you guys still read the list? I wanted to upload a new version of open-iscsi, but have not been able to reach you guys about troubles sshing into the web server. If you see this, email me. Or if someone knows their current emails addresses let me know. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: where is Dimitry and Alex (guys that manage open-iscsi.org)
Still here. There is a problem with the provider - they blocked our access for some strange reason. I'm going to try to fix this over the weekends! Mike Christie wrote: Hey, Dimitry or Alex, do you guys still read the list? I wanted to upload a new version of open-iscsi, but have not been able to reach you guys about troubles sshing into the web server. If you see this, email me. Or if someone knows their current emails addresses let me know. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
