open-iscsi Google Group

Debra Messing Covered Up

2008-09-06T04:00:48Z

The Will & Grace star gets caught nude!!
[link]

Re: [linux-iscsi-users] iscsi_tcp_recv wedges.

2008-09-05T17:00:48Z

Switching mailing lists since this should go to open-iscsi.
What is on the Dell box for Nics? Is is 1 gig or 10 gig? What manufacturer?
What is the newest kernel version you have tried? I do not think there
is a iscsi_tcp_recv function in newer kernels, so maybe you got the name
wrong when it flashed on the screen or it might be a older kernel.

Problem with iscsi

2008-09-05T08:11:13Z

Hi all.
I'm testing some iscsi configurations. Right now i have a iscsi target
on a solaris system and i get some errors when i use a linux initiator
with debian lenny and open-iscsi 2.0.869.
When i connect to a target, i always get this in the log:
Sep 5 10:02:56 srv-file kernel: scsi4 : iSCSI Initiator over TCP/IP

Re: open-iscsi creates the same device name as my root fs

2008-09-04T09:36:30Z

You are right, I think I got stuck with the /dev/xvd* device in the
new kernel

Thank you!

Re: open-iscsi creates the same device name as my root fs

2008-09-04T09:21:50Z

Carlos Acedo schrieb:
Yes, that's what I said in my previous mail (perhaps not clear enough):
"You have to use a different drive for domU" ;)

Re: open-iscsi creates the same device name as my root fs

2008-09-04T09:12:37Z

It seems there is another solution, changing the vm config with
something like this:

root = '/dev/sdi1 ro'
disk = [ 'file:/home/xen/domains/mail/d isk.img,sdi1,w', 'file:/home/
xen/domains/mail/swap.img,sdi2 ,w' ]

And the fstab as well, from sda to sdi

Using debian etch and Xen 3.3

Re: open-iscsi creates the same device name as my root fs

2008-09-03T12:05:44Z

Carlos Acedo schrieb:
Generally, it's a problem with Xen (running from upstream Xen 2.6.18
kernels). You have to use a different drive for domU.
You could try newer kernels, i.e. 2.6.26, with domU support compiled.
They have disks like /dev/xvd*, which don't collide with SCSI.

Re: open-iscsi creates the same device name as my root fs

2008-09-03T12:01:34Z

Yes, this is a domU, did you have the same problem?

Re: open-iscsi creates the same device name as my root fs

2008-09-03T11:56:48Z

Carlos Acedo schrieb:
Are you running Xen?

open-iscsi creates the same device name as my root fs

2008-09-03T11:52:46Z

Hello,

My root fs is /dev/sda1, when I login to my target open-iscsi (or
whatever is doing this) adds a device with the same name: sda1, so I
get:

$ cat /proc/partitions
major minor #blocks name

8 1 4194304 sda1 <-- rootfs
8 2 524288 sda2 <--- swap
8 0 780200960 sda <--- target

Re: [PATCH] Add compat patch for RHEL 5.2

2008-08-25T14:33:27Z

Hi Mike,
Various bits and pieces. For SLES10 SP2 I've updated the SCSI stack
to 2.6.22, so while the kernel version is still 2.6.16 the SCSI
midlayer is actually 2.6.22, hence the backport.
Sure:
We have CONFIG_SLE_VERSION and CONFIG_SLE_SP. So you should test for
CONFIG_SLE_VERSION == 10 && CONFIG_SLE_SP >= 2.

Re: [PATCH 2/4 2.6.28] cxgb3 - handle ARP replies for private iSCSI IP address

2008-08-25T13:45:42Z

On Fri, 22 Aug 2008 12:12:50 -0700
htons() goes through several levels of indirection to make sure
that if argument is constant, no code is necessary. The practice is
reserve __constant_htons() only for those cases like initialization and case
statements where C won't allow it.

Re: [PATCH 4/4 2.6.28] cxgb3i - cxgb3i iscsi driver

2008-08-23T19:31:38Z

Hi Andrew,
thanks for the review. We've started fixing the obvious and looking at
alternatives for the nofail allocations.
Cheers,
Divy

Re: open-iscsi looks broken on 2.6.27-rc4

2008-09-02T15:36:51Z

Yeah, the driver model code in the upstream kernel changed on us again,
so the patches have to be updated.

Re: open-iscsi logout errors

2008-09-02T15:35:30Z

I thin one of the iscsid process that handle the logout segfaulted.
Could you make sure you have one iscsid on your system by doing a
"whereis iscsid". Sometimes distro and older tools put them in different
places and you have to have the same iscsiadm and iscsid version.
If that is no help. Could you just run iscsid with lots of debugging