Using iSCSI On Ubuntu 9.04 (Initiator And Target)
I don't know if I'm missing something but when I'm mounting additional iSCSI volumes to a said server to add additional storage to a server I'm not seeing a way to mount the volume after running a discovery command.
The reasoning I want to be able to do this is that we're running an application that would require downtime everytime we add additional iSCSI volumes to this server.
I'm evaluating the possibility to use two off the shelf servers to build a cheap iSCSI redundant SAN. The idea is to run linux, pacemaker, and an iSCSI target - something like the SAN Active-Passive on linux-ha-examples.
The same page scares me a little when I read:
During the switchover of the iscsi-target one can detect a gap in the
protocol of write-test.log.
I have installed Fedora 17 to an iSCSI target by:
Booting with the Fedora 17 ISO
Chose LiveCD so I could install iscsi-initiator-utils
Started the installer
Chose iSCSI target from native Fedora installer
Installed as normal
Using iPXE (gpxe/etherboot fork) to boot with sanboot iscsi:HOSTIP::::TARGET:LUN, but Fedora bombs after about 10 seconds with the following errors:
Cannot open font file
AllI am having some trouble on getting a LVM volume that is hosted on a iSCSI target to mount on boot. Trying to figure out why that would be.On the iSCSI initiator side, I... [by bchand]
There is iSCSI initiator on CentOS 6.2. If the connection is terminated on TCP/IP, file sharing is not restored to the disk because the operating system assumes the target device file system ... [by DrBim]
This question is a follow-on from Dedicated NIC or dedicated port for iSCSI?
Excluding the hardware iSCSI initiator point that was made in the accepted answer to the above question, it seems that using separate port(s) on a multi-port NIC for iSCSI is pretty much going to meet the recommendation of using "seperate NICs" for iSCSI traffic.
I'm in the process of planning a small iSCSI installation
Ok I've been trying to get this working, but I need help.
I've been trying to get an iscsi target configured on my RHEL 5 server. The problem I keep running into is I tell it to login to a target, but everytime I reboot the server it finds and logs into every iscsi target available on the server.
First I need to know how to make it only connect and login to the one target.
When is iscsid starting up, before or after mounting filesystems? I suspect the iscsi subsystem isn't running until after the file systems are mounted... So your iSCSI isn't getting mount... [by dbhost3006]
Email this page
