iscsi through linux software bridge?
Has anyone been successful in setting up a linux software bridge and loging into an iscsi target? I've setup the following: Linux Target: == eth2 - 192.168.30.1 eth3 - 192.168.30.2 Linux Client: == eth2 - BRIDGE=iscsi0 iscsi0 - TYPE=Bridge iscsi0:1 - 192.168.30.3 eth3 - BRIDGE=iscsi1 iscsi1 - TYPE=Bridge iscsi1:1 - 192.168.30.4 I can discover all targets. But when I go to log into them, it fails. If I break the software bridges and just leave the IP's on eth2 and eth3, they can login and discover just fine. Thanks, Joe --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
iscsi through linux software bridge?
I dont' think I sent this properly to the list. This is my second attempt :) Has anyone been successful in setting up a linux software bridge and loging into an iscsi target? I've setup the following: Linux Target: == eth2 - 192.168.30.1 eth3 - 192.168.30.2 Linux Client: == eth2 - BRIDGE=iscsi0 iscsi0 - TYPE=Bridge iscsi0:1 - 192.168.30.3 eth3 - BRIDGE=iscsi1 iscsi1 - TYPE=Bridge iscsi1:1 - 192.168.30.4 I can discover all targets. But when I go to log into them, it fails. If I break the software bridges and just leave the IP's on eth2 and eth3, they can login and discover just fine. Thanks Joe --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Suse 10.2 install of open-iscsi 2.0-871
Okay, thats good to know, any idea when/if that will be done? Any idea what the last version of open-iscsi that does work on Suse? On Sep 30, 12:54 pm, Mike Christie micha...@cs.wisc.edu wrote: On 09/30/2009 11:07 AM, Taylor wrote: I am getting compile errros when running make KSRC=/usr/src/linux KBUILD_OUTPUT=/usr/src/linux-obj/x86_64/smp on a Suse 10.2 machine. I made sure the Cryptographic API and CRC32 options were set to Yes in kernel. I believe the problem is the 2.6.16-suse.patch isn't being run before the compile problems occur. The SUSE patch does not work with the current modules. It needs to be updated. --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Request to get open-iscsi working on Suse 10.2
I've seen several posts about people wanting to upgrade version of open-iscsi on Suse 10.2, but responsea re it doesn't compile, problem with patch, etc. So can this be considered a formal request to get someone to look at getting it to compile again on Suse 10.2? Can one of the developers provide an ETA as to when they think this can be done? Thanks, Taylor --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
SLES11 / udev rules / tape media changer
Dear all,
at our SLES11 server there is an iscsi tape roboter from OVERLAND
attached.
We learnt to use udev rules in order to fix the device name for the
media changer
/dev/sgN where N is altering after each reboot.
Here is the udevinfo output of our tape changer:
#udevinfo -a -p $(udevinfo -q path -n /dev/sg5)
looking at device
'/devices/platform/host4/session1/target4:0:0/4:0:0:2/scsi_generic/
sg5':
KERNEL==sg5
SUBSYSTEM==scsi_generic
DRIVER==
looking at parent device
'/devices/platform/host4/session1/target4:0:0/4:0:0:2':
KERNELS==4:0:0:2
SUBSYSTEMS==scsi
DRIVERS==
ATTRS{device_blocked}==0
ATTRS{type}==8
ATTRS{scsi_level}==6
ATTRS{vendor}==OVERLAND
ATTRS{model}==NEO Series
ATTRS{rev}==0510
ATTRS{tgps}==1
ATTRS{state}==running
ATTRS{timeout}==0
ATTRS{iocounterbits}==32
ATTRS{iorequest_cnt}==0xe
ATTRS{iodone_cnt}==0xe
ATTRS{ioerr_cnt}==0x3
ATTRS{modalias}==scsi:t-0x08
ATTRS{evt_media_change}==0
ATTRS{queue_depth}==32
ATTRS{queue_type}==none
Therefore we built a new rule called 100-local.rules in /etc/udev/
rules.d with
this line:
KERNEL==sg*, SUBSYSTEMS==scsi, ATTRS{rev}==0510, SYMLINK
+=loader0
After running /etc/init.d/boot.udev restart we would expect to see
/dev/loader0. But it does'nt exist, why?
THX for any hint advice,
Rainer
--~--~-~--~~~---~--~~
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
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
iscsid died and kernel module screwed?
Hi there, We hit a iscsid die case. use ps -ef|grep iscsid, we only saw one iscsid process. Unfortunately, we didn't enable debug log so there are not many logs available. We looked at the iscsid log it states that it received some kernel reported error. Also, in the kernel log, there is OOP complaints. After that, we used open-iscsi init script to restart, but the kernel modules were not been able to removed. We issue iscsiadm -m session, it gives: r...@swe_1_ser_2:~# iscsiadm --mode session tcp: [17] []:-1,1 \ufffd\ufffd?\ufffd|0\ufffdHYw The iscsiadm --mode session -P 3 hangs: r...@swe_1_ser_2:~# iscsiadm --mode session -P 3 iSCSI Transport Class version 2.0-870 iscsiadm version 2.0-870 Target: \ufffd\ufffd?\u04cbA\ufffd\ufffd\ufffd? Current Portal: []:-1,1 Persistent Portal: []:-1,1 ** Interface: ** Iface Name: .bss Iface Transport: tcp Iface Initiatorname: iqn.1993-08.org.debian:01:f0de76895ed6 Iface IPaddress: [192.168.1.99] Iface HWaddress: default Iface Netdev: default SID: 17 iscsid log: Sep 29 13:00:05 swe_1_ser_2 iscsid: Kernel reported iSCSI connection 16:0 error (1011) state (3) Sep 29 13:00:05 swe_1_ser_2 iscsid: Kernel reported iSCSI connection 17:0 error (1011) state (3) Sep 29 13:00:10 swe_1_ser_2 iscsid: connect failed (111) Sep 29 13:00:10 swe_1_ser_2 iscsid: connect failed (111) Sep 29 13:00:17 swe_1_ser_2 iscsid: connect failed (111) Sep 29 13:00:17 swe_1_ser_2 iscsid: connect failed (111) Sep 29 13:00:23 swe_1_ser_2 iscsid: connect failed (111) Sep 29 13:00:23 swe_1_ser_2 iscsid: connect failed (111) kernel log: Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8459.978988] connection16:0: ping timeout of 15 secs expired, last rx 2035865, last ping 2038365, now 2042115 Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8459.979351] connection16:0: detected conn error (1011) Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8460.094535] connection17:0: ping timeout of 15 secs expired, last rx 2035894, last ping 2038394, now 2042144 Sep 29 13:00:05 swe_1_ser_2 kernel: [ 8460.094733] connection17:0: detected conn error (1011) Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.129711] session16: session recovery timed out after 120 secs Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.129860] session17: session recovery timed out after 120 secs Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133734] sd 373:0:0:75: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133747] end_request: I/O error, dev sdd, sector 1638144 Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133753] Buffer I/O error on device sdd, logical block 204768 Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133873] sd 374:0:0:78: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133878] end_request: I/O error, dev sde, sector 24 Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.133881] Buffer I/O error on device sde, logical block 3 Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134087] sd 373:0:0:75: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134093] end_request: I/O error, dev sdd, sector 1638144 Sep 29 13:02:05 swe_1_ser_2 kernel: [ 8580.134097] Buffer I/O error on device sdd, logical block 204768 Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655094] sd 374:0:0:78: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655101] end_request: I/O error, dev sde, sector 1638144 Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655349] sd 374:0:0:78: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Sep 29 13:02:23 swe_1_ser_2 kernel: [ 8597.655356] end_request: I/O error, dev sde, sector 0 Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.193745] BUG: unable to handle kernel NULL pointer dereference at virtual address 0060 Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.193951] printing eip: e08ce12a *pde = Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.194234] Oops: [#1] SMP Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.194407] Modules linked in: ipt_REJECT iscsi_tcp libiscsi scsi_transport_iscsi iscsi_trgt crc32c libcrc32c nls_iso8859_1 nls_cp437 vfat fat vmmemctl cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_stats freq_table cpufreq_powersave sbs video output sbshc dock battery iptable_filter ip_tables x_tables vmhgfs lp loop ipv6 container serio_raw ac i2c_piix4 button intel_agp i2c_core agpgart shpchp pci_hotplug parport_pc parport evdev psmouse pcspkr ext3 jbd mbcache sr_mod cdrom pata_acpi ata_generic sg sd_mod floppy pcnet32 ata_piix mii mptspi mptscsih mptbase scsi_transport_spi libata scsi_mod raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0 multipath linear md_mod dm_mirror dm_snapshot dm_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse vmxnet Sep 29 13:02:25
Re: iscsid died and kernel module screwed?
We use 2.0-870.3. The kernel is Ubuntu 8.04 with kernel 2.6.24-24. We get the open-iscsi modules and tools from open-iscsi.org. Thanks. Kevin On Thu, Oct 1, 2009 at 1:19 PM, Mike Christie micha...@cs.wisc.edu wrote: On 09/30/2009 03:27 PM, Kevin Ye wrote: Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195515] Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195623] Pid: 5839, comm: iscsid Not tainted (2.6.24-24-generic #1) Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.195719] EIP: 0060:[e08ce12a] EFLAGS: 00010202 CPU: 0 Sep 29 13:02:25 swe_1_ser_2 kernel: [ 8600.196041] EIP is at spi_device_match+0x1a/0x60 [scsi_transport_spi] This is a little strange. What version of open-iscsi are you using? Where did you get the kernel or what distro is this? Are you using the distro's iscsi modules and tools or are they from open-iscsi.org? --~--~-~--~~~---~--~~ 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 open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
