On Tue, Dec 15, 2009 at 12:26 PM, DeepBlue wrote:
> There is a error with I inserting the ib_iser.ko module as following:
>
> [r...@localhost init.d]# insmod /lib/modules/2.6.18-8.el5/kernel/
> drivers/infiniband/ulp/iser/ib_iser.ko
> insmod: er
On 15 Dec 2009 at 22:47, shyam_i...@dell.com wrote:
> From the spec:
> "
>CHAP secrets MUST be an integral number of bytes (octets). A
>compliant implementation SHOULD NOT continue with the login step in
>which it should send a CHAP response (CHAP_R, Section 11.1.4
>Challenge Hands
On 15 Dec 2009 at 18:18, Xintao Zhang wrote:
> Hey all
> Therer is a error with inserting the ib_iser.ko as following:
> ==
> [r...@localhost init.d]# insmod
Generally you should use "modprobe" instead of "insmod". I have no idea on your
specific problem, howe
Hi,
Using open-iscsi-2.0.869-8.1 (x86_64) on a SUSE 11.0 based machine,
connecting to an HP D2D.
Generally operation seems fine but I have some issues:-
I cannot get the system to reconnect as start, if I configure open-isci to
start at boot
the system hangs, I have to do a force reboot
There is a error with I inserting the ib_iser.ko module as following:
[r...@localhost init.d]# insmod /lib/modules/2.6.18-8.el5/kernel/
drivers/infiniband/ulp/iser/ib_iser.ko
insmod: error inserting '/lib/modules/2.6.18-8.el5/kernel/drivers/
infi
Hey all
Therer is a error with inserting the ib_iser.ko as following:
==
[r...@localhost init.d]# insmod
/lib/modules/2.6.18-8.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko
insmod: error inserting
'/lib/modules/2.6.18-8.el5/kernel/drivers/infiniband/ulp/iser/
I run open-iscsi with a error as following:
=
[r...@localhost init.d]# ./open-iscsi start
Starting iSCSI initiator service: FATAL: Error inserting ib_iser (/lib/
modules/2.6.18-8.el5/kernel/drivers/infiniband/ulp/iser/ib_iser.ko):
Unknown symbol in module
> -Original Message-
> From: devel-boun...@open-fcoe.org [mailto:devel-boun...@open-fcoe.org]
> On Behalf Of Eric Multanen
> Sent: Tuesday, December 15, 2009 10:31 AM
> To: de...@open-fcoe.org
> Subject: [Open-FCoE] [fcoemon PATCH v2 00/11] rfcoemon restructuring
>
> v2 - restore code in t
>From the spec:
"
CHAP secrets MUST be an integral number of bytes (octets). A
compliant implementation SHOULD NOT continue with the login step in
which it should send a CHAP response (CHAP_R, Section 11.1.4
Challenge Handshake Authentication Protocol (CHAP)) unless it can
verify tha
On 12/14/2009 08:25 PM, Yangkook Kim wrote:
> I posted similar message on other thread, but let me ask the same question
> with diffrent tittle.
>
> I want to make a kernel compat patch without "kernel/" sub-directory.
> I used "git diff" to output the patch, but each header of outputted
> patch i
On Tue, Dec 15, 2009 at 10:34 AM, Mike Christie wrote:
> Erez Zilber wrote:
>> Maintain a list of nop-out PDUs that almost timed out.
>> With this information, you can understand and debug the
>> whole system: you can check your target and see what caused
>> it to be so slow on that specific time,
On 15 Dec 2009 at 10:32, Geoff Galitz wrote:
>
> > You might want to post to linux-kernel or linux-scsi list. The iscsi
> > initiator does not control this, but I think there are some scsi or
> > block layer tools that can do it if the target/disk supports it.
>
> I'll do that. I did try to use
> You might want to post to linux-kernel or linux-scsi list. The iscsi
> initiator does not control this, but I think there are some scsi or
> block layer tools that can do it if the target/disk supports it.
I'll do that. I did try to use sgmode to enable this, but that just did not
work.
-geoff
Hey,
I made a open-iscsi-2.0-871.1 release with the following fixes over 2.0-871:
Don't kill iscsid if logout from all nodes fail
iscsid: fix ISCSI_ERR_INVALID_HOST err handling
iscsid: add flag to indicate if driver needs iscsid to set ip
iscsid: add be2iscsi templat
vagrant wrote:
> It seems to be related to below url:
> http://groups.google.com/group/open-iscsi/browse_thread/thread/06e3bf8da91c466a
>
> A bug was logged and was similar to below descriptions:
> https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/289470
I have a new tarball. We are havin
galitz wrote:
> Hello,
>
> I am connecting to iSCSI targets on a QNAP TS-439U. They connect as
> write-through cache enabled, but I cannot seem to tune the cache on
> the QNAP side. Is there a way to enable/configure write back cache on
> the Linux initiator side?
>
You might want to post to l
vagrant wrote:
> Hi, All
>
> I am a novice, and I successfully installed iscsi-target on Linux.
> I just wonder if a Linux open-iscsi as a Host, and then install a
> iscsi-target for win on Windows, can they be access to each other?
> Thanks a lot.
>
Yes.
--
You received this message b
Just email the trace to me in private.
Anuarg Vora wrote:
> I have got a reproducible test case for this.
> It seems that SCSI layer returns DID_BUS_BUSY many times when 'conn error
> (1011)' is seen.
>
DID_BUS_BUSY when getting a 1011 is sort of expected. If you are not
using dm-multipath the
Erez Zilber wrote:
> Maintain a list of nop-out PDUs that almost timed out.
> With this information, you can understand and debug the
> whole system: you can check your target and see what caused
> it to be so slow on that specific time, you can see if your
> network was very busy during that time
19 matches
Mail list logo
