similar to: Possible to run iscsi-target and initiator on same server?

Hello, Need anyone's help regarding issues I encountered during make on iscsitarget-1.40.20 which I get from "svn co https://iscsitarget.svn.sourceforge.net/svnroot/iscsitarget/trunkiscsitarget" checkout revision 481 Issues where found below after a series of my command, as shown: [junix at thesisQRMproject iscsitarget]$ make *cc:

I'm having trouble updating my iscsitarget modules, and it seems to be related to a naming convention mixup? here's the output of the build command: [root at vmhost ~]# rpmbuild --rebuild --sign iscsitarget-0.4.14.96-0.amherst.src.rpm Installing iscsitarget-0.4.14.96-0.amherst.src.rpm error: Failed build dependencies: kernel-devel = 2.6.9-42.0.10.ELlarge is needed by

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root at localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1

Hello Experts, When I try to create SR with lvm over iSCSI, it always failed, I list my xe command and debug info: [root@xcp16 log]# xe sr-create host-uuid=a226200e-f7ff-4dee-b679-e5f114d1e465 content-type=user name-label=shared_disk_sr shared=true device-config:target=192.168.1.2 device-config:targetIQN=iqn.2013-07.example:shareddisk device-config:SCSIid=1IET_00010001 type=lvmoiscsi The SR is

Hi all, I have the strangest problem on one of our backup server. iscsi doesn't start at all, and gives the following error: [root at 2U-NAS ~]# /etc/init.d/iscsi status iscsid is stopped [root at 2U-NAS ~]# /etc/init.d/iscsi start iscsid is stopped Starting iSCSI daemon: Unable to create pid file: /var/run/brcm_iscsiuio.pid [FAILED] Setting up iSCSI targets: iscsiadm: No records

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

Hello, I'm fairly new to centos and to iscsi, I have installed a fresh copy of centos (CentOS release 5 (Final)) and installed iscsi-initator-utils, iscsiadm -V shows iscsiadm version 2.0-865 . when i try to connect to iscsi target it doesnt work ... it just stays idle , i try something like: iscsiadm -m discovery -t st -p 172.20.2.76 show or with -m node .... --login ...etc, none works.

Does anyone know off hand how to bind iscsi enterprise target to two distinct addresses. Lets say I have a machine that has a bunch of interfaces on it, with different subnets. Rather than have ietd broadcast itself on all interfaces (the default), I would like to limit it to only two interfaces. I have edited the init.d startup script with --address x.x.x.x which works, but I tried using the

Hi, I'd like to know what would be the best way to remove an iscsi lvm storage from a server. (removing all reference to that storage etc.) The storage in question will be reset and reformated and used on a different server; so no LVM export is needed. Do I have to do lvremove ..., vgremove ..., pvremove ... and do an iscsiadm -m node -T ... -p ... -u and iscsiadm -m node -o delete -T ...

Hi, How do I setup multiple password protected iSCSI targets on Linux? I know that mounting a password protected iSCSI target requires modify these records with the appropriate values: node.session.auth.username = My_ISCSI_USR_NAME node.session.auth.password = MyPassword discovery.sendtargets.auth.username = My_ISCSI_USR_NAME discovery.sendtargets.auth.password = MyPassword But, now I need

This hotplug script has been tested with IET and NetBSD iSCSI targets, without authentication. This hotplug script will only work with PV guests not using pygrub. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: Ian Jackson <ian.jackson@citrix.com> --- Changes due to 4.3 release freeze: * We can no longer provide a

Hi, Is it possible to discover iSCSI targets using libvirt API..? OR is it possible to get the similar results of below commands using libvirtAPI..? iscsiadm --mode discovery --type sendtargets --portal server1.example.com sudo iscsiadm -m discovery -t st -p 192.168.0.10 Regards Sijo

Hello All. I've just started looking into Xen and have a test environment in place. I'm seeing an annoying problem that I thought worthy of a post. Config: I have 2 x HP DL585 servers each with 4 Dual core Opterons (non-vmx) and 16GB RAM configured as Xen servers. These run CentOS 5.1 with the latest updates applied. These system both attach to an iSCSI target which is an HP DL385

Hi! I'm new to libvirt and face problems connecting to an iSCSI target. What I intend to do is to connect libvirt (I tried virt-manager and virsh) to an iSCSI target and then boot from the LUNs which contain the VMs. I followed the documentation¹ but got stuck at section 12.1.5.4.3. 1) virsh pool-define-as \ --name foo \ --type iscsi

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

Hello, thanks for the help. Yes And the commands to discovery iscsi results ok Such iscsiadm --mode discovery --type sendtargets And scsiadm -m node -T And the disks appear on pvdisplay 2018-03-14 16:23 GMT-03:00 Marcelo Roccasalva < marcelo-centos at irrigacion.gov.ar>: > On Wed, Mar 14, 2018 at 4:08 PM, marcos sr <msr.mailing at gmail.com> wrote: > > > >

I am fairly new to ISCSI and SAN technology but having recently invested in the technology I am trying to find out exactly what can and can not be manipulated, filesystem wise, without requiring a reboot. I am using the inbuilt software ISCSI initiator and multipathing in CentOS 5.1. My steps so far. Create 10GB volume on SAN # iscsiadm -m session -R # fdisk /dev/mapper/mpath0 # kpartx -a

Two questions (and then a bonus one), kind of interrelated, but, first, some basic info. I'm using OCFS2 on OpenSUSE 10.2, kernel 2.6.18.8(-0.7). There are three nodes in the OCFS2 cluster, backed by Openfiler iSCSI storage. First, I'm using Openfiler and iSCSI volumes to back my OCFS2 file system. The nodes that are part of the OCFS2 cluster use the file system as a shared storage

> This should already be useful, at least for file-based disks. It''d be > nice to > have the ENBD script working and have some kind of iSCSI script at some > stage. For iSCSI, have a look at iscsi-init at sourceforge. http://iscsi-init.sourceforge.net. Load it as a module in an initrd and it uses some kernel parameters and automatically configures the network and then