open-iscsi Google Group

Re: open-iscsi crosscompile try for mips arch. help required!

hein...@googlemail.com (heini66) — Sat, 20 Mrz. 2010 09:00:43 UT

2010/3/18 Martin <hein...@googlemail.com>
a real path in my cflags that the compiler findes the includes in
src/include and the files in src/usr.
atm i'm stucking at:
open-iscsi-2.0-871/utils/sysde ps/
open-iscsi-2.0-871/utils/sysde ps/Makefile
open-iscsi-2.0-871/utils/sysde ps/sysdeps.c
set -e; shopt -s nullglob; for i in make/open-iscsi/patches/*.patc h; do

Re: FW: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

ravi.an...@qlogic.com (Ravi Anand) — Fri, 19 Mrz. 2010 22:48:35 UT

In the current state *iscsi netlink interface* does not allow the user space
apps for iSCSI H/W offload solution (in our case its qla4xxx) to pass down bunch
of parameter's in one shot for configuration purposes. As of know one can pass
one param at a time using netlink but that does not fit very well for offload

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

micha...@cs.wisc.edu (Mike Christie) — Fri, 19 Mrz. 2010 21:11:18 UT

Yeah, you are right. That should go in a separate patch and sent later.

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

fujita.tomon...@lab.ntt.co.jp (FUJITA Tomonori) — Thu, 18 Mrz. 2010 23:10:36 UT

On Thu, 18 Mar 2010 16:02:52 -0500
Yeah, seems you are right. But looks like this patchset also adds the
vendor specific message support (ISCSI_BSG_HST_VENDOR)?
I still want to know why vendors can't do this via the existing
netlink interface. open-iscsi uses the netlink interface for some pdu
so I guess that having a different channel for management might be a

Re: open-iscsi against sun storage tek 2500 fails: 1011 error.

oriol.mor...@urv.cat (Oriol Morell) — Fri, 19 Mrz. 2010 10:04:06 UT

Mike,
any suggestion? thxs.
Oriol

Mike,

we have done the following two commands. Please find attached the
output files.
tcpdump -i eth0 tcp port 3260 and host
192.168.192.136
-w /root/tcpdumpIPandPort3260.dum p
tcpdump -i eth0 host 192.168.192.136 -w /root/tcpdumpIPandNada.dump

Checking these files with wireshark, an error found is "TCP Previous

open-iscsi crosscompile try for mips arch. help required!

hein...@googlemail.com (Martin) — Thu, 18 Mrz. 2010 22:29:51 UT

hi there,
i'm tring to crosscompile for mips arch.
build fails with:
/home/heini66/freetz-trunk/sou rce/open-iscsi-2.0-871/utils/
fwparam_ibft'
/home/heini66/freetz-trunk/too lchain/target/bin/mipsel-linux -uclibc-
gcc -Os -pipe -march=4kc -Wa,--trap -D_LARGEFILE_SOURCE -
D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -c -DLINUX -c -o

Re: Using failover with differing EUI / IQN values

tehb...@gmail.com (Claude Bing) — Fri, 19 Mrz. 2010 17:31:03 UT

Does this still apply if I'm using two separate iSCSI target devices sharing
the same data source (RAID)?
On Mar 19, 2010 1:24 PM, "Alex Zeffertt" <alex.zeffe...@eu.citrix.com>
wrote:
Yes, I've done it!
multipathd uses /sbin/scsi_id to determine which block devices are really
the same as eachother. (Actually, the callout is configured in

Re: Using failover with differing EUI / IQN values

alex.zeffe...@eu.citrix.com (Alex Zeffertt) — Fri, 19 Mrz. 2010 17:23:51 UT

Yes, I've done it!
multipathd uses /sbin/scsi_id to determine which block devices are really the
same as eachother. (Actually, the callout is configured in /etc/multipath.conf,
but its usually /sbin/scsi_id).
If /sbin/scsi_id returns the same ID for two block devices then you should be
able to failover between them.

Using failover with differing EUI / IQN values

tehb...@gmail.com (Claude Bing) — Fri, 19 Mrz. 2010 17:11:30 UT

Hello,
I am wondering if it is possible to failover an iSCSI path from one EUI /
IQN to one with a different EUI / IQN assuming the data on both targets is
identical. Would this be handeled by the iSCSI stack or multipathd?
Thank you for your help!

What happens if an iSCSI target resets.

al...@iplink.net (Alvin Starr) — Fri, 19 Mrz. 2010 14:12:52 UT

I am thinking of a 2 node cluster that sync the disks via DRBD.
I have seen some articles about using multipath and 2 independent
targets but have also seen generic problem descriptions of using
multipath in the face of failures.
I was thinking of using a floating IP address for the target and using

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

james.sm...@emulex.com (James Smart) — Fri, 19 Mrz. 2010 12:56:30 UT

Separate this request into two needs:
The first need is for the iscsi driver to have some kind of entry point to
kick off a vendor specific thing - primarily diagnostics and internal f/w and
flash mgmt items. Here, using the same mechanism that we had on the FC side,
which also supports dma payloads, made a lot of sense. I like and prefer the

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

micha...@cs.wisc.edu (Mike Christie) — Thu, 18 Mrz. 2010 21:02:52 UT

I think this is what Jay is not trying to do. I think the patch has some
extra code like the ISCSI_BSG_HST_VENDOR parts that makes it confusing -
it got me too. The ISCSI_BSG_HST_VENDOR code in be2iscsi looks like it
is basically disabled (should remove for a formal patch when he sends
for merging).

Re: [PATCH 2/2] RFC: The be2iscsi driver support for bsg

fujita.tomon...@lab.ntt.co.jp (FUJITA Tomonori) — Thu, 18 Mrz. 2010 13:58:37 UT

On Wed, 17 Mar 2010 23:37:07 +0530
So this patchset adds the user-kernel space interface for management
via bsg, right?
Then I have two questions.
- open-iscsi already has the user-kernel space interface for
management via netlink. Why do you need another via bsg? IOW, why
can't you do this via the existing netlink interface?

Re: [PATCH 1/2] RFC: Proposal for BSG Interface

bharr...@panasas.com (Boaz Harrosh) — Thu, 18 Mrz. 2010 12:55:36 UT

What? where? who? how? why? w*\? ...
You are proposing a new Kernel ABI/API here right. I think it is not acceptable
without a detailed documentation, including every little bit. Nothing missing.
If lots of it is already written for FC then grate most of your job is done.
But for us mortals please put some text on an introductory message. I use iscsi

Fwd: target creation and isns scn notification

gopu.0...@gmail.com (Gopu Krishnan) — Thu, 18 Mrz. 2010 05:10:38 UT

Hi All,
Can someone look into this issue as mentioned in the below mail thread.
I feel this is an BUG. If not please clarify on the same.
Thanks
Gopal.
---------- Forwarded message ----------
To: open-iscsi@googlegroups.com
Hi All,
In IET code, we create the target before the isns init. I understand that