Re: iferror -38

chava45 wrote: > Mike, > Here is the log information from /var/log/messages. > > Jan 27 14:02:04 rac1 iscsid: iSCSI logger with pid=4380 started! > Jan 27 14:02:05 rac1

CHAP with Open-iSCSI

Hi Mike, We are using Open iSCSI initiator with our iSCSI target. I have a question on CHAP. I did some experiment and it appears to me that OneWay-CHAP does not work with open-iscsi, Mutual-CHAP does work fine for me. Have others seen the same behavior? Thx, Arvind. --~--~-~--~~---

Re: CHAP with Open-iSCSI

Arvind Jain wrote: > Hi Mike, > We are using Open iSCSI initiator with our iSCSI target. > I have a question on CHAP. > I did some experiment and it appears to me that OneWay-CHAP does not work > with open-iscsi, Mutual-CHAP does work fine for me. > Have others seen the same behavior? Not really

Re: CHAP with Open-iSCSI

Mike Christie wrote: > Arvind Jain wrote: >> Hi Mike, >> We are using Open iSCSI initiator with our iSCSI target. >> I have a question on CHAP. >> I did some experiment and it appears to me that OneWay-CHAP does not work >> with open-iscsi, Mutual-CHAP does work fine for me. >> Have others seen t

RE: CHAP with Open-iSCSI

Mike, I have attached the wire shark trace for OneWay-CHAP and Mutual-CHAP. I am not sure how helpful this is. In case of OneWay-CHAP, Open-iscsi initiator does not continues with the login step and gives and error as follows: Logging in to [iface: default, target: iqn.2008-07.com.wasabi:osd.1,

Re: iferror -38

Mike , In response to the following update by you... --- Either you are hitting the bug I thought I fixed or these nops are really timing out. I am downloading open filer now to test it out here. --

Re: iferror -38

Mike , Can you also let me know if there is any workaround on this issue? On Jan 28, 10:42 am, chava45 wrote: > Mike , > In response to the following update by you... > --- > Either you are hitting the bug I thought I fixed

loopback interface IP problem

Hi there. I'm mounting a standard iscsi target. I've been doing a lot of interesting nice things, I can see the disk, I can play with it and everything is very wonderfull ! :) Long story short, the disk has been running fine as if it was really attached. The problem started when I had the need t

Re: CHAP with Open-iSCSI

Arvind Jain wrote: > Mike, > I have attached the wire shark trace for OneWay-CHAP and Mutual-CHAP. I am > not sure how helpful this is. > > In case of OneWay-CHAP, Open-iscsi initiator does not continues with the > login step and gives and error as follows: > > Logging in to [iface: default, ta

Re: iferror -38

chava45 wrote: > Mike , > Can you also let me know if there is any workaround on this issue? > Yeah, if this is the bug I thought I fixed then you can just turn off nops. Are you using dm-multipath? They are mostly useful for fast failovers when using multipath. You can turn them off by setti

Re: loopback interface IP problem

PECastro wrote: > Hi there. > > I'm mounting a standard iscsi target. > I've been doing a lot of interesting nice things, I can see the disk, > I can play with it and everything is very wonderfull ! :) Long story > short, the disk has been running fine as if it was really attached. > > The probl

PATCH: fix iBFT firmware reading with newer kernels

Hi, While testing I noticed that "iscsiadmin -m fw" does not work properly on newer (rawhide atleast) kernels, the attached patch (already applied to the Fedora devel packages) fixes this. Regards, Hans --~--~-~--~~~---~--~~ You received this message because yo

PATCH: do not use exit()

Hi All, While testing I noticed that idbm_lock() uses exit when it cannot lock, leading to interesting effect when using it from libiscsi, when typing "import libiscsi" in python as normal user, my entire python interpreter exited, not good. The attached patch instead returns an error code, an

Filesystem corruption using iser transport

Hello Open-IScsi-Group! We use infiniband for our storage backend. Recently we managed to get iscsi-over ISER to work with stgtd 0.9.3 (build from tgz) and open-iscsi 2.0.870 (Debian package) on Debian Lenny. Running tiotest we get impressive performance but also filesystem corruption [45343.0

Re: PATCH: fix iBFT firmware reading with newer kernels

Hans de Goede wrote: > Hi, > > While testing I noticed that "iscsiadmin -m fw" does not work properly on > newer > (rawhide atleast) kernels, the attached patch (already applied to the Fedora > devel packages) fixes this. > Did you port this from another file/version? Not sure what I was th

RE: CHAP with Open-iSCSI

Mike, I have the following info as you requested: [r...@localhost ~]# iscsid -d 8 -f iscsid: sysfs_init: sysfs_path='/sys' iscsid: sysfs_attr_get_value: open '/module/scsi_transport_iscsi'/'version' iscsid: sysfs_attr_get_value: new uncached attribute '/sys/module/scsi_transport_iscsi/version'

RE: CHAP with Open-iSCSI

Oops, forgot to attach the login debug info using "iscsid -d 8 -f &" last time. Debug output attached for oneway-CHAP and Mutual-CHAP. Mutual-CHAP works fine with our target. Thx, Arvind. -Original Message- From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] On Behalf

Re: CHAP with Open-iSCSI

On 28 Jan 2009 at 12:06, Mike Christie wrote: > > Arvind Jain wrote: > > Hi Mike, > > We are using Open iSCSI initiator with our iSCSI target. > > I have a question on CHAP. > > I did some experiment and it appears to me that OneWay-CHAP does not work > > with open-iscsi, Mutual-CHAP does work

Re: loopback interface IP problem

On 28 Jan 2009 at 11:06, PECastro wrote: > > Hi there. > > I'm mounting a standard iscsi target. > I've been doing a lot of interesting nice things, I can see the disk, > I can play with it and everything is very wonderfull ! :) Long story > short, the disk has been running fine as if it was re