Re: iSCSI LUN mount on boot
Claudio Jeker writes:
> Yeah, the documentation is not great.
>
> You need to add 'net' to the mount options in /etc/fstab for iscsi drives.
> Then our rc script will do the right thing and mount these drives late
> (after iscsid started).
>
> .a /mnt/test ffs rw,noatime,nodev,nosuid,net 1 2
>
> With that it should work. You can not use iscsi for /, /usr, /var but it
> works for /home or /var/www.
Thanks Claudio for the note. Unfortunately, this was not
successful. Slightly different, but ultimately the same problem.
When the machine comes up, it does indeed pass mounting all of the local
partitions before trying to mount the iSCSI target.
However, it still blows up and enters single user mode. Upon entering
single user mode, the additional NIC that connects to the SAN does
appear to be configured and happy (I can ping the iSCSI host). You can
see pictures of the screen before [1] and after [2] entering and exiting
single user mode. In [3], you can see the machine does eventually hit a
login prompt.
Upon exiting single user mode, it then gives an error message that
"SIOCSIFGATTR" is an invalid argument to ifconfig, before continuing to
boot. It then says iscsid failed to start. This is visible in [2] and [3].
Once actually logged in, it appears as though iscsid is dead in the
water. However, if I remove the /etc/fstab entry, it boots as normal and
then I can mount manually as expected. Very strange.
Checking /var/log/daemon, this is what I see:
Feb 20 18:59:28 elara iscsid[52173]: startup
Feb 20 18:59:28 elara iscsid[52173]: fatal in iscsid: vscsi_open: Device busy
Diagnostic info to follow. dmesg is also attached.
I'm wondering if this is a misconfiguration on my part, or more
potentially is it a bug? This is on a fresh install of today's -current
snapshot - I'm rebuilding the machine due to hardware failure/upgrades
and can't say I've actually tried to do this before, so can't say it
worked before. It is just odd to me to that the drive mounts fine
manually, but blows up when trying to mount on boot.
Hopefully, somebody can provide some answers. Please let me know if any
further info is required.
Thanks,
Ash
[1] https://thalassa.fagg.id.au/IMG_6318.jpg
[2] https://thalassa.fagg.id.au/IMG_6321.jpg
[3] https://thalassa.fagg.id.au/IMG_6322.jpg
Diagnostic info:
Here is my full and complete /etc/fstab. /build is the mount-point in
question. It is my intention to (hopefully) mount it at /usr/ports, but
just for the sake of troubleshooting I tried a different mountpoint.
I also tried the exact same options Claudio suggested with the same
result.
elara$ cat /etc/fstab
02215eb188a74570.b none swap sw
02215eb188a74570.a / ffs rw 1 1
02215eb188a74570.k /home ffs rw,nodev,nosuid 1 2
02215eb188a74570.d /tmp ffs rw,nodev,nosuid 1 2
02215eb188a74570.f /usr ffs rw,nodev 1 2
02215eb188a74570.g /usr/X11R6 ffs rw,nodev 1 2
02215eb188a74570.h /usr/local ffs rw,wxallowed,nodev 1 2
02215eb188a74570.j /usr/obj ffs rw,nodev,nosuid 1 2
02215eb188a74570.i /usr/src ffs rw,nodev,nosuid 1 2
02215eb188a74570.e /var ffs rw,nodev,nosuid 1 2
08b434e6d3d1d227.c /build ffs rw,noatime,nodev,wxallowed,net 1 2
Here is my full and complete /etc/iscsid.conf:
elara$ cat /etc/iscsi.conf
target "ports" {
initiatoraddr 172.16.0.2
targetaddr 172.16.0.1
targetname "iqn.2011-01.au.id.fagg.ctl:elara-usr-ports"
}
And the two NIC configs + an ifconfig:
elara$ cat /etc/hostname.re0
inet 192.168.1.6 0xff00
elara$ cat /etc/hostname.ix0
inet 172.16.0.2 0xf000
up
elara$ doas ifconfig
doas (f...@elara.fagg.id.au) password:
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
ix0: flags=8843 mtu 1500
lladdr 90:e2:ba:29:76:a0
index 1 priority 0 llprio 3
media: Ethernet autoselect (10GSFP+Cu full-duplex,rxpause,txpause)
status: active
inet 172.16.0.2 netmask 0xf000 broadcast 172.16.15.255
re0: flags=8843 mtu 1500
lladdr 70:85:c2:67:19:b9
index 2 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 192.168.1.6 netmask 0xff00 broadcast 192.168.1.255
enc0: flags=0<>
index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33136
index 5 priority 0 llprio 3
groups: pflog
dmesg attached below:
OpenBSD 6.9-beta (GENERIC.MP) #346: Fri Feb 19 23:56:21 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 42861899776 (40876MB)
avail mem = 41547546624 (39622MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed2d0 (33 entries)
bios0: vendor American Megatr
Re: iSCSI LUN mount on boot
On Fri, Feb 19, 2021 at 07:48:25PM -0500, Ashton Fagg wrote: > I'm curious as to what other folks are doing for mounting iSCSI volumes > at boot time. I've successfully configured iscsid, and mounting the > volume manually works as expected. > > I found this article [1] which suggests that hotplugd should be used. > > I also found this old presentation [2] which suggests it should "just > work" with an entry in /etc/fstab. Maybe I did not get this correct, as: > > .a /mnt/test ffs rw,noatime,nodev,nosuid,nofail 1 2 > > causes the machine to go into single-user mode on boot (presumably > because the iSCSI daemon hasn't yet started). > > Am I missing something here? Is hotplugd the preferred way to accomplish this? Yeah, the documentation is not great. You need to add 'net' to the mount options in /etc/fstab for iscsi drives. Then our rc script will do the right thing and mount these drives late (after iscsid started). .a /mnt/test ffs rw,noatime,nodev,nosuid,net 1 2 With that it should work. You can not use iscsi for /, /usr, /var but it works for /home or /var/www. -- :wq Claudio
iSCSI LUN mount on boot
I'm curious as to what other folks are doing for mounting iSCSI volumes at boot time. I've successfully configured iscsid, and mounting the volume manually works as expected. I found this article [1] which suggests that hotplugd should be used. I also found this old presentation [2] which suggests it should "just work" with an entry in /etc/fstab. Maybe I did not get this correct, as: .a /mnt/test ffs rw,noatime,nodev,nosuid,nofail 1 2 causes the machine to go into single-user mode on boot (presumably because the iSCSI daemon hasn't yet started). Am I missing something here? Is hotplugd the preferred way to accomplish this? Thanks. [1]: https://www.bsdhowto.ch/automount.html [2]: https://www.slideshare.net/eurobsdcon/claudio-iscsid
iSCSI in recent Supermicro boards
Hello. Does anybody know about iSCSI BIOS settings in recent Supermicro boards? For example, manual for X8SIL family says: 1-7 iSCSI Support The X8SIL/X8SIL-F/X8SIL-V motherboard supports the iSCSI Internet Protocol. iSCSI is an IP networking standard used to link and manage data storage, and transfer data across the internet and private intranets through long distance. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet. It can enable location-independent data storage and retrieval. iSCSI allow clients to issue SCSI commands to remote SCSI storage devices and allow data centers to consolidate remote storage devices into storage arrays, giving an illusion of locally-attached disks to host servers. Unlike fiber-optic networks that require special cabling, iSCSI can run over long distance using existing networks. For the X8SIL/X8SIL-F/X8SIL-V motherboard, iSCSI is supported on LAN 1. This can be enabled through the BIOS: Advanced = PCI/PnP Configuration = Onboard LAN1 Option ROM Select. Please see Chapter 4 for details. Is it booting over iSCSI support? A kind of iSCSI packet prioritization? Smth else? Thanks. Alexey
Re: iSCSI in recent Supermicro boards
This is some kind of BIOS boot-up support The chips on this board are run-of-the-mill em OpenBSD 4.9-current (GENERIC.MP) #32: Sat Apr 23 18:16:16 PDT 2011 ch...@celery.ykwc.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8580038656 (8182MB) avail mem = 8337596416 (7951MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9f000 (68 entries) bios0: vendor American Megatrends Inc. version 1.1 date 05/27/2010 bios0: Supermicro X8SIL acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SSDT EINJ BERT ERST HEST acpi0: wakeup devices P0P1(S4) P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) BR1E(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) USB5(S4) USB6(S4) GBE_(S4) BR20(S4) BR21(S4) BR22(S4) BR23(S4) BR24(S4) BR25(S4) BR26(S4) BR27(S4) EUSB(S4) USBE(S4) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2400.33 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 133MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2400.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2400.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2400.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 7 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 7 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (P0P3) acpiprt3 at acpi0: bus 2 (P0P5) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus 6 (BR1E) acpiprt6 at acpi0: bus 3 (BR20) acpiprt7 at acpi0: bus 4 (BR24) acpiprt8 at acpi0: bus 5 (BR25) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpicpu2 at acpi0: C3, C2, C1, PSS acpicpu3 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 2400 MHz: speeds: 2401, 2400, 2267, 2133, 2000, 1867, 1733, 1600, 1467, 1333, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core DMI rev 0x11 ppb0 at pci0 dev 3 function 0 Intel Core PCIE rev 0x11: apic 7 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 5 function 0 Intel Core PCIE rev 0x11: apic 7 int 16 pci2 at ppb1 bus 2 Intel Core Management rev 0x11 at pci0 dev 8 function 0 not configured Intel Core Scratch rev 0x11 at pci0 dev 8 function 1 not configured Intel Core Control rev 0x11 at pci0 dev 8 function 2 not configured Intel Core Misc rev 0x11 at pci0 dev 8 function 3 not configured Intel Core QPI Link rev 0x11 at pci0 dev 16 function 0 not configured Intel Core QPI Routing rev 0x11 at pci0 dev 16 function 1 not configured ppb2 at pci0 dev 28 function 0 Intel 3400 PCIE rev 0x05: apic 7 int 17 pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 4 Intel 3400 PCIE rev 0x05: apic 7 int 17 pci4 at ppb3 bus 4 em0 at pci4 dev 0 function 0 Intel PRO/1000 MT (82574L) rev 0x00: apic 7 int 16, address 00:25:90:0d:63:f0 ppb4 at pci0 dev 28 function 5 Intel 3400 PCIE rev 0x05: apic 7 int 16 pci5 at ppb4 bus 5 em1 at pci5 dev 0 function 0 Intel PRO/1000 MT (82574L) rev 0x00: apic 7 int 17, address 00:25:90:0d:63:f1 ehci0 at pci0 dev 29 function 0 Intel 3400 USB rev 0x05: apic 7 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb5 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xa5 pci6 at ppb5 bus 6 vga1 at pci6 dev 3 function 0 Matrox MGA G200eW rev 0x0a wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 31 function 0 Intel 3400 LPC rev 0x05 ahci0 at pci0 dev 31 function 2 Intel 3400 AHCI rev 0x05: apic 7 int 19, AHCI 1.3 ahci0: invalid ata_xfer state 06 in ahci_put_ccb, slot 31 ahci0: invalid ata_xfer state 06 in
iSCSI NAS/SAN for claudio@
hello, i would encourage people to consider sending donations in for this, i think it would be an extremely good investment. claudio already has a good start on an implementation of an iscsi initiator, but he's at the point where he needs real gear to work and test against. given the gear i fully expect him to be able to make progress pretty quickly, which in turn means the rest of us can then use it. aside from the usefulness of it, i would love to see some iscsi code done the OpenBSD Way(tm) out in the wild too. cheers, dlg Begin forwarded message: From: Claudio Jeker clau...@cvs.openbsd.org Date: 11 February 2010 7:38:40 PM AEST To: source-chan...@cvs.openbsd.org Subject: CVS: cvs.openbsd.org: www CVSROOT: /cvs Module name: www Changes by: clau...@cvs.openbsd.org 2010/02/11 02:38:39 Modified files: . : want.html Log message: I'm looking for a rack-mountable iSCSI capable NAS/SAN for iSCSI initiator developement.
Re: iSCSI status
On Tue, Jan 19, 2010 at 08:08:51PM +1000, David Gwynne wrote: On 19/01/2010, at 7:04 PM, Michael Lechtermann wrote: Hi, Is it already possible to mount iSCSI devices with OpenBSD(-current)? no. You're such a pessimist, dlg. -- :wq Claudio
Re: iSCSI status
On 30/01/2010, at 10:34 PM, Claudio Jeker wrote: On Tue, Jan 19, 2010 at 08:08:51PM +1000, David Gwynne wrote: On 19/01/2010, at 7:04 PM, Michael Lechtermann wrote: Hi, Is it already possible to mount iSCSI devices with OpenBSD(-current)? no. You're such a pessimist, dlg. so prove me wrong :)
iSCSI status
Hi, Is it already possible to mount iSCSI devices with OpenBSD(-current)? Michael
Re: iSCSI status
On 19/01/2010, at 7:04 PM, Michael Lechtermann wrote: Hi, Is it already possible to mount iSCSI devices with OpenBSD(-current)? no.
iSCSI boot on OpenBSD
Hi all,
I am trying to find some info to boot an openbsd from a SAN (iSCSI). Is it
possible with the latest openbsd release?
Thanks.
--
CL Martinez
carlopmart {at} gmail {d0t} com
Re: iSCSI boot on OpenBSD
On Tue, 01 Dec 2009 19:30:27 +0100 carlopmart carlopm...@gmail.com wrote: Hi all, I am trying to find some info to boot an openbsd from a SAN (iSCSI). Is it possible with the latest openbsd release? Thanks. No. - Robert
Re: iSCSI boot on OpenBSD
On Wed, Dec 2, 2009 at 8:44 AM, Robert rob...@openbsd.pap.st wrote: On Tue, 01 Dec 2009 19:30:27 +0100 carlopmart carlopm...@gmail.com wrote: Hi all, I am trying to find some info to boot an openbsd from a SAN (iSCSI). Is it possible with the latest openbsd release? Thanks. No. - Robert It would be possible with a RAM disk if OpenBSD had something like pivot_root or switch_root for Linux, but AFAIK no such capability exists. You could do PXE boot and mount NFS shares for root - this process is well documented in the FAQ. HTH -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Re: iSCSI boot on OpenBSD
Aaron Mason wrote:
On Wed, Dec 2, 2009 at 8:44 AM, Robert rob...@openbsd.pap.st wrote:
On Tue, 01 Dec 2009 19:30:27 +0100
carlopmart carlopm...@gmail.com wrote:
Hi all,
I am trying to find some info to boot an openbsd from a SAN
(iSCSI). Is it possible with the latest openbsd release?
Thanks.
No.
- Robert
It would be possible with a RAM disk if OpenBSD had something like
pivot_root or switch_root for Linux, but AFAIK no such capability
exists. You could do PXE boot and mount NFS shares for root - this
process is well documented in the FAQ.
HTH
Maybe can I use pxe/nfs solution ... Ok, I will try it.
Many thanks to all for your help.
--
CL Martinez
carlopmart {at} gmail {d0t} com
OpenBSD iSCSI
Hello,. i am in need to setup a box to works as a iSCSI target. My operating system of choice is OpenBSD. I found netbsd iSCSI and would like to install it on OpenBSD. Does anybody already implemented it on OpenBSD? Is there any thing i should be aware about it? Thanks in advance. Best Regards, FL.
Re: OpenBSD iSCSI
On Thu, 11 Jun 2009 14:03:43 -0300, Friedrich Locke wrote Hello,. i am in need to setup a box to works as a iSCSI target. My operating system of choice is OpenBSD. I found netbsd iSCSI and would like to install it on OpenBSD. Does anybody already implemented it on OpenBSD? Is there any thing i should be aware about it? Thanks in advance. Best Regards, FL. You must have missed these two answers you already received about this last week: viz: http://marc.info/?l=openbsd-miscm=124406451918402w=2 http://marc.info/?l=openbsd-miscm=124406624521776w=2
OT: Granting access from DMZ servers to iSCSI network
Hi all,
Sorry for the off-topic but I need some help with a specific implemantation. I
have two OpenBSD firewalls with 4 interfaces each one: one for internal lan, one
for sync lan, one for dmz lan and another for Internet access.
I need to grant access from dmz servers to iscsi storage servers located on
internal lan. Which can be the best form to accomplish this??
a) Connect DMZ servers directly to iscsi servers using another private lan.
b) connect DMZ servers to iscsi server using private lan but using openbsd
firewalls to grant access to iscsi network
c) Using a third openbsd firewall (with a snort IDS to control traffic
content) configured as a bridge between DMZ servers and iSCSI servers ..
Any other solution??
Many thanks for your help.
--
CL Martinez
carlopmart {at} gmail {d0t} com
Re: OT: Granting access from DMZ servers to iSCSI network
On Fri, 2008-12-12 at 15:05 +0100, carlopmart wrote: Sorry for the off-topic but I need some help with a specific implemantation. I have two OpenBSD firewalls with 4 interfaces each one: one for internal lan, one for sync lan, one for dmz lan and another for Internet access. I need to grant access from dmz servers to iscsi storage servers located on internal lan. Which can be the best form to accomplish this?? Depends on how you define 'best' ;) a) Connect DMZ servers directly to iscsi servers using another private lan. Simplest approach. Works for some. b) connect DMZ servers to iscsi server using private lan but using openbsd firewalls to grant access to iscsi network Do you mean another interface/vlan for iscsi on the same physical OpenBSD firewalls? Wouldn't do it. I'd keep iscsi and all the rest strictly separated. Problem is when your OpenBSD setup is under heavy load or even DOS'ed you may get nasty scsi timeouts on the dmz servers. scsi isn't really tolerant ;) I saw linux servers just freeze because of that. c) Using a third openbsd firewall (with a snort IDS to control traffic content) configured as a bridge between DMZ servers and iSCSI servers .. Sounds reasonable. Don't know about the snort part, but you can also use pf on that bridge ... -- Stephan A. Rickauer --- Institute of Neuroinformatics Tel +41 44 635 30 50 University / ETH Zurich Sec +41 44 635 30 52 Winterthurerstrasse 190 Fax +41 44 635 30 53 CH-8057 ZurichWebwww.ini.uzh.ch
Re: OpenBSD and iSCSI support
Marco Peereboom wrote: Eventually. I started writing the qli driver but have not had time to finish that. I also am planning to do a software initiator/target using softraid however that is further out. *sigh* so much code so little time... So the information under http://en.wikipedia.org/wiki/ISCSI#Operating-system_support about OpenBSD supporting iSCSI is nonsense? On Sun, Jul 06, 2008 at 07:43:09PM +0200, Denis Fondras wrote: Hello, I'm doing some testing with iSCSI and I'd like to know if there is any plan to add iSCSI support to OpenBSD (initiator and/or target) ? Denis -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341
Re: OpenBSD and iSCSI support
On 8/8/08, Heinrich Rebehn [EMAIL PROTECTED] wrote: So the information under http://en.wikipedia.org/wiki/ISCSI#Operating-system_support about OpenBSD supporting iSCSI is nonsense? The information under http://en.wikipedia.org/wiki/ is nonsense.
Re: OpenBSD and iSCSI support
Yes. On Fri, Aug 08, 2008 at 11:09:25AM +0200, Heinrich Rebehn wrote: Marco Peereboom wrote: Eventually. I started writing the qli driver but have not had time to finish that. I also am planning to do a software initiator/target using softraid however that is further out. *sigh* so much code so little time... So the information under http://en.wikipedia.org/wiki/ISCSI#Operating-system_support about OpenBSD supporting iSCSI is nonsense? On Sun, Jul 06, 2008 at 07:43:09PM +0200, Denis Fondras wrote: Hello, I'm doing some testing with iSCSI and I'd like to know if there is any plan to add iSCSI support to OpenBSD (initiator and/or target) ? Denis -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341
Re: OpenBSD and iSCSI support
Eventually. I started writing the qli driver but have not had time to finish that. I also am planning to do a software initiator/target using softraid however that is further out. *sigh* so much code so little time... Thank you for the answer. Could you share what you've done please ? Denis
Re: OpenBSD and iSCSI support
What part isn't clear? On Mon, Jul 07, 2008 at 08:18:51PM +0200, Denis Fondras wrote: Eventually. I started writing the qli driver but have not had time to finish that. I also am planning to do a software initiator/target using softraid however that is further out. *sigh* so much code so little time... Thank you for the answer. Could you share what you've done please ? Denis
OpenBSD and iSCSI support
Hello, I'm doing some testing with iSCSI and I'd like to know if there is any plan to add iSCSI support to OpenBSD (initiator and/or target) ? Denis
Re: OpenBSD and iSCSI support
Eventually. I started writing the qli driver but have not had time to finish that. I also am planning to do a software initiator/target using softraid however that is further out. *sigh* so much code so little time... On Sun, Jul 06, 2008 at 07:43:09PM +0200, Denis Fondras wrote: Hello, I'm doing some testing with iSCSI and I'd like to know if there is any plan to add iSCSI support to OpenBSD (initiator and/or target) ? Denis
Re: iSCSI
A quick Google search shows some people having success in porting NetBSD's iSCSI to OpenBSD. perhaps Marco will chime in on this. diana If testers for an iSCSI initiator on OpenBSD should be needed, I am glad to help out. I run i386.mp-current and sparc64-current on servers that can access two iSCSI IP arrays from EqualLogic (3 and 7 TB), and a homebrew iSCSI target array (2.3 TB) running FreeNAS, over GigEthernet with Jumbo frame and (partial) multipath I/O support.. Rolf
iSCSI
Hi :), quick question: how can I connect OpenBSD box to iSCSI storage ? Best regards, Artur
Re: iSCSI
On Thu, Oct 18, 2007 at 04:13:35PM +0200, Artur Litwinowicz wrote: Hi :), quick question: how can I connect OpenBSD box to iSCSI storage ? by means of an iSCSI cable? cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: iSCSI
mickey wrote: On Thu, Oct 18, 2007 at 04:13:35PM +0200, Artur Litwinowicz wrote: quick question: how can I connect OpenBSD box to iSCSI storage ? by means of an iSCSI cable? While that's true, I'm guessing he already has an Ethernet cable... A quick Google search shows some people having success in porting NetBSD's iSCSI to OpenBSD.
Re: iSCSI
On Thu, 18 Oct 2007, Steve Shockley wrote: mickey wrote: On Thu, Oct 18, 2007 at 04:13:35PM +0200, Artur Litwinowicz wrote: quick question: how can I connect OpenBSD box to iSCSI storage ? by means of an iSCSI cable? While that's true, I'm guessing he already has an Ethernet cable... A quick Google search shows some people having success in porting NetBSD's iSCSI to OpenBSD. perhaps Marco will chime in on this. diana
Re: iSCSI
On 10/18/07, Diana Eichert [EMAIL PROTECTED] wrote: On Thu, 18 Oct 2007, Steve Shockley wrote: mickey wrote: On Thu, Oct 18, 2007 at 04:13:35PM +0200, Artur Litwinowicz wrote: quick question: how can I connect OpenBSD box to iSCSI storage ? by means of an iSCSI cable? While that's true, I'm guessing he already has an Ethernet cable... A quick Google search shows some people having success in porting NetBSD's iSCSI to OpenBSD. perhaps Marco will chime in on this. diana I don't know what's in the works, but currently you can only share out volumes on Open, it doesn't connect to iSCSI volumes. You need to get the Net code Steve mentioned to serve iSCSI. I think Mickey is talking about a bacon stretcher, which might work in this case. -jesse
iSCSI support
Hi, I'd like to know if OpenBSD dev team is interested or is planning to include iSCSI support in source tree. I know that NetBSD has recently implemented a Target iSCSI support (not Initiator), but NetBSD is not OpenBSD... Thanks Fulvio
NetBSD imported iSCSI framework
quote from http://www.netbsd.org/Changes/#iscsi-target 22 Feb 2006 - NetBSD iSCSI Status and HOWTOs (top) Alistair G. Crooks has recently added support for an iSCSI target to NetBSD, and written HOWTOs for using it. iSCSI is specified in RFC 3720 and describes a method for encapsulating SCSI commands in TCP/IP to remotely access block-level storage. In iSCSI, the party offering a SCSI device (the server) is called a target, and the party using that device (the client) is called an initiator, so the iSCSI target exports blocks to the iSCSI initiators.
Re: iscsi support
Kenneth R Westerback wrote: Nobody is working on iSCSI as far as I know, and I'm one of the scsi developers at OpenBSD. Now if someone was to donate enough equipment that someone could work on it, things might change. Ken Adaptec do a iscsi HBA, would you some more Adaptec kit? ;) A example of a working software target can be found here: http://iscsitarget.sourceforge.net/ potential candidate for openiscsi? Sevan
