Re: [ofa-general] Re: [Ips] Calculating the VA in iSER header

On Wed, Apr 16, 2008 at 6:46 PM, Roland Dreier <[EMAIL PROTECTED]> wrote: > > Agree with the interpretation of the spec, and it's probably a bit > > clearer that way too. But we have working initiators and targets > > that do it the "wrong" way. > > Yes... I guess the key question is whethe

iscsid segfaulting when running 'iscsiadm -k 0'

With the 869-rc4 and a SLES10 SP2 kernel with the 869-rc4 drivers compiled out of the tree I can get: iscsid[27598]: segfault at 2b4327f11000 rip 0040981b rsp 7fff826f61a0 error 4 when I run the 'iscsiadm -k 0' command. I haven't dug deep in this yet, but was wondering if some

connection2:0: detected conn error (1011).. when rebooting the machine hangs the reboot sequence.

Firstly, I haven't dug in this yet but this is more of a call: "have-you-seen-this-too?" When I reboot the machine without logging off from iSCSI targets I can hang the reboot sequence. This is with 869-rc4 userspace, SLES 10 SP2 Beta kernel, with a 869-rc4 kernels compiled out of tree. (With a

Re: debian/ directory in open-iscsi tarballs

On Tue, Apr 15, 2008 at 12:02 PM, Mike Christie <[EMAIL PROTECTED]> wrote: > I am fine with removing. I did not create or add it, and have no idea if > someone is using it. If there are users of it what is the alternative > that I should point people to. I can add a note to the README. I don

Re: iscsid segfaulting when running 'iscsiadm -k 0'

Konrad Rzeszutek wrote: > With the 869-rc4 and a SLES10 SP2 kernel with the 869-rc4 drivers compiled > out of > the tree I can get: > > iscsid[27598]: segfault at 2b4327f11000 rip 0040981b rsp > 7fff826f61a0 error 4 > > when I run the 'iscsiadm -k 0' command. > > I haven't dug

Re: connection2:0: detected conn error (1011).. when rebooting the machine hangs the reboot sequence.

Konrad Rzeszutek wrote: > Firstly, I haven't dug in this yet but this is more of a call: > "have-you-seen-this-too?" > This is probably on the list 20 times :) > When I reboot the machine without logging off from iSCSI targets I can > hang the reboot sequence. This is with 869-rc4 userspace, S

Can't discover large number of targets with open-iscsi

When I have 255 targets configured on my iscsi target, openiscsi can only discover 160 of them. Windows initiator can discover all of them. Have you seen this problem before? I am using open-iscsi-2.0-865.15.tar.gz Thanks, Simone --~--~-~--~~~---~--~~ You recei

Re: iscsid segfaulting when running 'iscsiadm -k 0'

On Thu, Apr 17, 2008 at 11:16:34AM -0500, Mike Christie wrote: > > Konrad Rzeszutek wrote: > > With the 869-rc4 and a SLES10 SP2 kernel with the 869-rc4 drivers compiled > > out of > > the tree I can get: > > > > iscsid[27598]: segfault at 2b4327f11000 rip 0040981b rsp > > 7fff

Re: connection2:0: detected conn error (1011).. when rebooting the machine hangs the reboot sequence.

> It looks like the network is off but the session is still running. We > eventually get to the kernel shutoff here. Is your init script getting > run? If not then run it. If you left the session on on purpose then you > cannot turn the network off because the scsi layer will want to do its >

Re: Can't discover large number of targets with open-iscsi

Simone Morellato wrote: > > When I have 255 targets configured on my iscsi target, openiscsi can only > discover 160 of them. > Windows initiator can discover all of them. > Have you seen this problem before? > > I am using open-iscsi-2.0-865.15.tar.gz > Try http://www.open-iscsi.org/bits/ope

Re: BUG: scheduling while atomic: scsi_wq_5/0x10000001/7047

On Apr 11, 1:29 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > Kamil Kisiel wrote: > > I'm running open-iscsi-2.0.868 on a Linux 2.6.21 Xen DomU kernel. I > > was this open-iscsi-2.0.868 test1 or rc1? > > > > > find that when doing heavy I/O, particularly between two iSCSI > > targets, I receive