interaction with udev
Hello, I have installed 2.0.865 on a Debian Etch system. I can use my targets withyout any problem. However when I stop open-iscsi my devices (/dev/sdb e.g.) aren't removed from the system. I can still access them without any problems. I can remove them with scsiadd -r But then restarting open-iscsi doesn't bring them back. An other problem I have is that when I start open-iscsi devices are added by udev under /dev/disk/by-path/. When stopping open-iscsi links under /dev/disk/by-path aren't removed. I think that is because the raw devices are still available. Anybody seen this problem? Or thought about it? Thanks in advance, Rudy --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Hi Don, Don Williams wrote: > Hello Rudy, > > > > If you run ps -ax | grep iscsid after you stop open-iscsi I suspect > you'll find that the daemon is still running. In deed. > > > [EMAIL PROTECTED]:~# ps ax | grep iscsid > > 5651 ?Ss 0:07 /sbin/iscsid > > 5652 ?S > 15984 pts/2S+ 0:00 grep iscsid > > > > > > You'll see that there are multiple iscsid running.The > start-stop-daemon in debian doesn't handle the multiple PIDs. > > > > My really poor fix is to add a 'killall -1 iscsid' to the > /etc/init.d/open-iscsi script. <...> > > > I know I’ll probably get flamed for such a poor fix but it works for > me. ;-) > > > > I do recall that someone posted a suggested proper fix for debian but > it didn’t get added. You fix kills all the iscsid programs. But I still have the device /dev/sdb e.g. available. :( -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep SystemenSystems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Andrew Moise wrote: > On Mon, Mar 31, 2008 at 8:42 AM, Rudy Gevaert <[EMAIL PROTECTED]> wrote: >> I have installed 2.0.865 on a Debian Etch system. >> I can use my targets withyout any problem. >> >> However when I stop open-iscsi my devices (/dev/sdb e.g.) aren't removed >> from the system. I can still access them without any problems. > > What's the full output when you attempt to stop open-iscsi? It > sounds like your open-iscsi system may simply not be getting shut down > because of an error. I've seen my Debian system get into a state > where the init scripts didn't work because the current state of > open-iscsi wasn't consistent; in my case rebooting the system solved > the problem (though it would be better to make the init scripts more > robust against this problem). > Cheers. I rebooted the system. open-iscsi starts by default. I have iscsid running: jlyj43j:~# ps aux | grep iscsid root 2606 0.0 0.0 2868 444 ?Ss 15:37 0:00 /usr/sbin/iscsid root 2607 0.0 0.0 3352 2328 ?Shttp://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Andrew Moise wrote: > On Mon, Mar 31, 2008 at 10:01 AM, Rudy Gevaert <[EMAIL PROTECTED]> wrote: >> I'm stopping with init script of debian: >> >> jlyj43j:~# /etc/init.d/open-iscsi stop >> Disconnecting iSCSI targets:. >> Stopping iSCSI initiator service:. >> >> Iscsid is still running: >> >> jlyj43j:~# ps aux | grep iscsid >> root 2606 0.0 0.0 2868 444 ?Ss 15:37 0:00 >> /usr/sbin/iscsid >> root 3277 0.0 0.0 2732 616 pts/0R+ 15:43 0:00 grep iscsid > > That's very unfortunate. How did you install 2.0.865 on an etch > system? Did you do a backport of the sid packages, or did you compile > the tarball? Did you ever have the Debian etch package (or any > earlier package) installed? > Thanks. I backported the version in lenny. That because rescan isn't available in the older release. I upgraded from the version in Etch. Rudy -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep SystemenSystems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Konrad Rzeszutek wrote: > On Mon, Mar 31, 2008 at 02:42:24PM +0200, Rudy Gevaert wrote: >> Hello, >> >> I have installed 2.0.865 on a Debian Etch system. >> I can use my targets withyout any problem. >> >> However when I stop open-iscsi my devices (/dev/sdb e.g.) aren't removed >> from the system. I can still access them without any problems. >> >> I can remove them with >> scsiadd -r > > Ugh. That is bad. > > Have you tried to logout? That should have taken care of removing > the block devices. iscsiadm -m node --logoutall=all (if that is what you mean) doesn't give me any output. And /dev/sdb is still on my system. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep SystemenSystems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Don Williams wrote: > Can you try the 2.0-865 build and compile it? > > I use that version with debian without any issues. Hi Don, I'm using that version already Rudy -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur Direction ICT, Infrastructure dept. Groep Systemen Systems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Hi Mike Mike Christie wrote: > > What is the version of your kernel? 2.6.18-6-xen-amd64 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur Direction ICT, Infrastructure dept. Groep Systemen Systems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Hi Mike, Mike Christie wrote: > Rudy Gevaert wrote: >> Hi Mike >> >> Mike Christie wrote: >> >>> What is the version of your kernel? >> >> 2.6.18-6-xen-amd64 >> > > Make sure you are using the kernel modules from the open-iscsi.org > release, start up iscsi, then run: I'm not sure I understand what you are saying. I'm running a stock Debian kernel with modules provided by Debian. So I should compile open-iscsi (the version I'm running) against the kernel I'm running. (And thus not using the modules in the kernel by Debian?). > iscsiadm -m session -P 3 > iscsiadm -m node -U all -d 8 > iscsiadm -m session -P 3 > > And send the outpout from all 3 commands. The middle one is going to > print out a lot of stuff, but send it all. Attached! Thanks in advance, Rudy -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep SystemenSystems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~--- iscsiadm -m session -P 3: iSCSI Transport Class version 1.1-646 iscsiadm version 2.0-865 Target: iqn.1992-08.com.netapp:sn.101194508:vf.23898710-f515-11dc-a9d9-00a09806b742 Current Portal: 172.16.223.6:3260,1007 Persistent Portal: 172.16.223.6:3260,1007 ** Interface: ** Iface Name: default Iface Transport: tcp Iface IPaddress: default Iface HWaddress: default Iface Netdev: default SID: 0 iSCSI Connection State: LOGGED IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 65536 FirstBurstLength: 65536 MaxBurstLength: 65536 ImmediateData: Yes InitialR2T: No MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 1 State: running scsi1 Channel 00 Id 0 Lun: 0 Attached scsi disk sdb State: running scsi1 Channel 00 Id 0 Lun: 1 Attached scsi disk sdc State: running scsi1 Channel 00 Id 0 Lun: 2 Attached scsi disk sdd State: running iscsiadm -m node -U all -d 8 iscsiadm: Could not open /sys/class/iscsi_host/host1/initiatorname. iscsiadm: Could not read initiatorname for host 1. Error 2 iscsiadm: Could not open /sys/class/iscsi_host/host1/ipaddress. iscsiadm: Could not read ipaddress for host 1. Error 2 iscsiadm: Could not open /sys/class/iscsi_host/host1/hwaddress. iscsiadm: Could not read hwaddress for host 1. Error 2 iscsiadm: Could not open /sys/class/iscsi_host/host1/netdev. iscsiadm: Could not read netdev for host 1. Error 2 iscsiadm: in read_transports iscsiadm: Adding new transport iser iscsiadm: Adding new transport tcp iscsiadm: Could not open /sys/class/iscsi_host/host1/hwaddress. iscsiadm: could not read hwaddress for /sys/class/iscsi_host/host1/hwaddress iscsiadm: in read_transports iscsiadm: Could not open /sys/class/iscsi_host/host1/ipaddress. iscsiadm: could not read local address for /sys/class/iscsi_host/host1/ipaddress iscsiadm: Could not open /sys/class/iscsi_host/host1/netdev. iscsiadm: could not read netdev for /sys/class/iscsi_host/host1/netdev iscsiadm: found targetname iqn.1992-08.com.netapp:sn.101194508:vf.23898710-f515-11dc-a9d9-00a09806b742 address 172.16.223.6 pers address 172.16.223.6 port 3260 pers port 3260 driver tcp iface ipaddress default netdev default hwaddress default iscsiadm: rec read looking for config file /etc/iscsi/nodes/iqn.1992-08.com.netapp:sn.101194508:vf.23898710-f515-11dc-a9d9-00a09806b742/172.16.223.6,3260. iscsiadm: rec read looking for config file /etc/iscsi/nodes/iqn.1992-08.com.netapp:sn.101194508
Re: interaction with udev
Mike Christie wrote: > Rudy Gevaert wrote: >> Hi Mike >> >> Mike Christie wrote: >> >>> What is the version of your kernel? >> >> 2.6.18-6-xen-amd64 >> > > Make sure you are using the kernel modules from the open-iscsi.org > release, start up iscsi, then run: As extra info: jlyj43j:~# modinfo libiscsi filename: /lib/modules/2.6.18-6-xen-amd64/kernel/drivers/scsi/libiscsi.ko author: Mike Christie :) description:iSCSI library functions license:GPL vermagic: 2.6.18-6-xen-amd64 SMP mod_unload gcc-4.1 depends:scsi_mod,scsi_transport_iscsi -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734 Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office Groep SystemenSystems group Universiteit Gent Ghent University Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: interaction with udev
Hello,
So it seems that running 2.6.18 (stock Debian kernel) with open-iscsi
2.0.730-1etch1 doesn't give me any problems regarding the start and
stopping. (Although one iscsid process is still running when I stop it
with the init script.)
Doing
echo - - - > /sys/class/scsi_host/hostX/scan
effectively rescans my target, so the need to upgrade to a later version
is not necessary (for me).
However using a later open-iscsi (2.0.865-1) has some problems on 2.6.18
kernel. It isn't really stopping when I stop it. The devices are still
available.
Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467390 has
some notes about the newer version of open-iscsi not working with
kernels below 2.6.25.
2.6.24 is in Debian unstable, without xen for amd64 and I need xen
support, so I'm rather stuck with 2.6.18.
Stopping open-iscsi also deletes the correct /dev/disk/by-path links.
But I'm still having problems with a udev rule I wrote myself:
jlyj43j:/etc/udev/rules.d# cat z99_netapp_persistant.rules
# This file contains the rules needed to create persistent device names.
# we are only interested in add actions for block devices
SUBSYSTEM!="block", GOTO="no_volume_id"
ACTION!="add", GOTO="no_volume_id"
# skip xen virtual hard disks
DRIVERS=="vbd", GOTO="no_hardware_id"
KERNEL=="sd*[!0-9]",\
IMPORT{program}="netappluns $KERNEL"
KERNEL=="sd*[!0-9]",
ENV{VFILER}=="?*",ENV{LUN}=="?*",ENV{VOLUME}=="?*",ENV{STATE}=="GOOD", \
SYMLINK+="disk/by-vfiler/$ENV{VFILER}/$ENV{VOLUME}/$ENV{LUN}"
# end of processing
LABEL="no_volume_id"
The problems seems to be a timing issue. My 'netappluns' script is
acting on /dev/sdX. But /dev/sdX isn't yet created by udev. Thus failing.
Calling udevtrigger manually, after /dev/sdX is created, creates the
relevant links.
Are there any guidelines for integrating udev with open-iscsi?
Thanks in advance,
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep SystemenSystems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: interaction with udev
Konrad Rzeszutek wrote:
> Get a multipath udev file. They are using mechanism to wait for the device
> to settle before acting on it. That might give you some ideas on how to
> remove the race conditions.
Unfortunate my setup only has the following rules:
clyj43j:/etc/udev/rules.d# cat z60_kpartx.rules
#
# persistent links for device-mapper devices
# only hardware-backed device-mapper devices (ie multipath, dmraid,
# and kpartx) have meaningful persistent device names
#
KERNEL!="dm-*", GOTO="kpartx_end"
ACTION=="remove", GOTO="kpartx_end"
# This is a temporary hack until Debian's dmsetup support "export" (#434241)
IMPORT{program}="/lib/udev/dmsetup_env %M %m"
ENV{DM_TABLE_STATE}!="LIVE", GOTO="kpartx_end"
ENV{DM_UUID}=="?*", IMPORT{program}=="kpartx_id %M %m $env{DM_UUID}"
OPTIONS="link_priority=50"
# Create persistent links for multipath tables
ENV{DM_UUID}=="mpath-*", \
SYMLINK+="disk/by-id/$env{DM_TYPE}-$env{DM_NAME}"
# Create persistent links for dmraid tables
ENV{DM_UUID}=="dmraid-*", \
SYMLINK+="disk/by-id/$env{DM_TYPE}-$env{DM_NAME}"
# Create persistent links for partitions
ENV{DM_PART}=="?*", \
SYMLINK+="disk/by-id/$env{DM_TYPE}-$env{DM_NAME}-part$env{DM_PART}"
# Create dm tables for partitions
ENV{DM_STATE}=="ACTIVE", ENV{DM_UUID}=="mpath-*", \
RUN+="/sbin/kpartx -a -p -part /dev/$kernel"
ENV{DM_STATE}=="ACTIVE", ENV{DM_UUID}=="dmraid-*", \
RUN+="/sbin/kpartx -a -p -part /dev/$kernel"
LABEL="kpartx_end"
And:
clyj43j:/etc/udev/rules.d# cat z60_multipath.rules
#
# udev rules for multipathing.
# The persistent symlinks are created with the kpartx rules
#
# socket for uevents
RUN+="socket:/org/kernel/dm/multipath_event"
In the kpartx_id and dmsetup_env programs I don't see anything relevant
that does any waiting. I could be looking over it...
What exactly do you mean?
Thanks in advance,
Rudy
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep SystemenSystems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: interaction with udev
Hi Mike,
Mike Christie wrote:
> Rudy Gevaert wrote:
>> Hello,
>>
>>
>> So it seems that running 2.6.18 (stock Debian kernel) with open-iscsi
>> 2.0.730-1etch1 doesn't give me any problems regarding the start and
>> stopping. (Although one iscsid process is still running when I stop it
>> with the init script.)
>
> That is a bug in iscsid not handling the kill signals right. Other
> scripts do a killall -9 iscsid type of thing but debian does not. Now
> iscsid handles the normal stop signals so there is no need to do killall -9.
I can say that it doesn't affect me if that one process is still
running. Or I haven't experienced any side effects.
>> Doing
>> echo - - - > /sys/class/scsi_host/hostX/scan
>> effectively rescans my target, so the need to upgrade to a later version
>> is not necessary (for me).
>>
>> However using a later open-iscsi (2.0.865-1) has some problems on 2.6.18
>> kernel. It isn't really stopping when I stop it. The devices are still
>>available.
>
> I do not think 2.0.865 works with the 2.6.18 upstream kernel. The
> interface was not stable until 2.6.21, so before that you had to upgrade
> tools with the kernel or the distro kernel had to be updated.
Correct, it works up to a certain hight.
>
>> Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467390 has
>> some notes about the newer version of open-iscsi not working with
>> kernels below 2.6.25.
>
> I am not sure if that is worded right. The scsi userspace interface we
> used was broken and that broke the open-iscsi tools. The newest version
> of open-iscsi tools contain a fix, but they require a kernel fix that
> is in 2.6.25.
>
> Alternatively, you can use the kernel modules and tools in the
> open-iscsi.org release because they have all the updated fixes.
>
> Also, I am not sure if this
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467390 affects you.
> With netapp targets (just guessing you have a netapp target because of
> the naming of your rule below) I think you can control the write back
> cache settings. If it is disabled like here:
Luckily it doesn't affect me.
> Apr 1 12:04:07 meanminna kernel: sd 9:0:0:8: [sdo] Write cache:
> disabled, read cache: enabled, doesn't support DPO or FUA
>
> then you will not hit the problem.
>
>
>> 2.6.24 is in Debian unstable, without xen for amd64 and I need xen
>> support, so I'm rather stuck with 2.6.18.
>>
>> Stopping open-iscsi also deletes the correct /dev/disk/by-path links.
>> But I'm still having problems with a udev rule I wrote myself:
>> Are there any guidelines for integrating udev with open-iscsi?
>>
>
> No. There are some threads on the list from users doing their custom
> scripts, but normally we probably prefer to user the distros default
> rules. If you have the most uptodate ones they should normally be fine
> for what you want to do. If they are not then we should talk about why not.
The default rules are ok for iscsi. I have know figured out the
following. If one is depending on /dev/device to be available then one
must use the RUN keyword. Executing programs with PROGRAM or
IMPORT{program} doesn't guarantee that /dev/device is available at the
moment the program is run. Using RUN guarantees that.
The downside of using RUN is that one has to manage everything by hand.
E.g. the adding/removal of symlinks.
Thank you for helping me getting to the bottom of this!
Rudy
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep SystemenSystems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
iscsiadm: Could not offload sendtargets
Hello I'm an trying to configure offloading with a qlogic hba. It is not all very clear to me. I have the following questions: 1) The hba gives me an extra interface. Should I have that interface an IP? 2) iscsiadm -m iface , gives me: default tcp iser iser qla4xxx.00:c0:dd:0e:e3:ad qla4xxx,00:c0:dd:0e:e3:ad,192.168.201.4,, I set an IP (after reading the README) on that iface: iscsiadm -m iface -I qla4xxx.00:c0:dd:0e:e3:ad # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = qla4xxx.00:c0:dd:0e:e3:ad iface.net_ifacename = iface.ipaddress = 192.168.201.4 iface.hwaddress = 00:c0:dd:0e:e3:ad iface.transport_name = qla4xxx iface.initiatorname = # END RECORD However when doing the discovery I get: iscsiadm -m discovery -t st -p 192.168.201.200:3260 -I qla4xxx.00:c0:dd:0e:e3:ad iscsiadm: Could not offload sendtargets to 192.168.201.200. Any pointers in getting me in the good direction is very much appreciated! Thanks Rudy -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
qlogic hba: Could not offload sendtargets
Hello, I'm trying to use a qlogic hba to do offloading. I don't fully understand anything. I am following the readme file. The following things aren't clear to me: 1) I get an extra interface (eth1). Should I give that interface an ip address? If I don't, I can't ping the target. What is this interface needed for? 2) I set an ip address on the iface reported by iscsiadm: r...@isis:/usr/share/doc/open-iscsi# iscsiadm -m iface default tcp iser iser qla4xxx.00:c0:dd:0e:e3:ad qla4xxx,00:c0:dd:0e:e3:ad,192.168.201.4,, r...@isis:/usr/share/doc/open-iscsi# iscsiadm -m iface -I qla4xxx.00:c0:dd:0e:e3:ad # BEGIN RECORD 2.0-871 iface.iscsi_ifacename = qla4xxx.00:c0:dd:0e:e3:ad iface.net_ifacename = iface.ipaddress = 192.168.201.4 iface.hwaddress = 00:c0:dd:0e:e3:ad iface.transport_name = qla4xxx iface.initiatorname = # END RECORD However, then discovery doesn't work: r...@isis:/usr/share/doc/open-iscsi# iscsiadm -m discovery -t st -p 192.168.201.200:3260 -I qla4xxx.00:c0:dd:0e:e3:ad iscsiadm: Could not offload sendtargets to 192.168.201.200. iscsiadm: initiator reported error (1 - unknown error) I'm running 2.6.32-5-xen-amd64 (Debian Squeeze) and 2.0.871.3-2squeeze1 of open-iscsi.. Any help in pointing me in the right direction is greatly appreciated. Thanks! Rudy -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: qlogic hba: Could not offload sendtargets
thanks for the pointer, I'll try that next week. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: qlogic hba: Could not offload sendtargets
Hi Pasi. In fact I didn't. I didn't know I needed some other tool. I will have to look into that. Thanks -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
