Skip to main content

iSCSI target RHEL 6

I'm currently attempting to become more familiar with the iSCSI targets on Linux... so, I anticipate that I will be adding to this post - but what I have documented here should get a person by...

# NOTE: I discovered this will not work on a VXFS mount if SELinux is enabled
# :-(

yum install iscsi-initiator-utils scsi-target-utils perl-Config-General
mkdir -p /var/lib/tgtd/
lvcreate -L500g -nlv_tgtd vg_blackmesa
mkfs.ext4 /dev/mapper/vg_blackmesa-lv_tgtd
echo "/dev/mapper/vg_blackmesa-lv_tgtd   /var/lib/tgtd  ext4 defaults 0 0" >> /etc/fstab

dd if=/dev/zero of=/var/lib/tgtd/iscsi-tgt-01.img bs=1m seek=100000 count=0
dd if=/dev/zero of=/var/lib/tgtd/iscsi-tgt-02.img bs=1m seek=100000 count=0
dd if=/dev/zero of=/var/lib/tgtd/iscsi-tgt-03.img bs=1m seek=100000 count=0
dd if=/dev/zero of=/var/lib/tgtd/iscsi-tgt-04.img bs=1m seek=100000 count=0
dd if=/dev/zero of=/var/lib/tgtd/iscsi-tgt-05.img bs=1m seek=100000 count=0

restorecon -RFvv /var/lib/tgtd/

cp /etc/tgt/targets.conf /etc/tgt/targets.conf.orig

tgtadm --lld iscsi --op new --mode target --tid=1 --targetname iqn.2012-05.private.area51.blackmesa:storage.target1
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b /var/lib/tgtd/iscsi-tgt-01.img
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 2 -b /var/lib/tgtd/iscsi-tgt-02.img
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 3 -b /var/lib/tgtd/iscsi-tgt-03.img
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 4 -b /var/lib/tgtd/iscsi-tgt-04.img
tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 5 -b /var/lib/tgtd/iscsi-tgt-05.img

cat <<EOF> /etc/tgt/targets.conf
<target iqn.2012-05.private.area51.blackmesa:storage.target1>
    backing-store /var/lib/tgtd/iscsi-tgt-01.img
    backing-store /var/lib/tgtd/iscsi-tgt-02.img
    backing-store /var/lib/tgtd/iscsi-tgt-03.img
    backing-store /var/lib/tgtd/iscsi-tgt-04.img
    backing-store /var/lib/tgtd/iscsi-tgt-05.img
    initiator-address 10.10.31.110
    initiator-address 10.10.31.111
</target>
EOF
service tgtd restart; chkconfig tgtd on
service iscsi restart; chkconfig iscsi on
service iscsid restart; chkconfig iscsid on

tgtadm --lld iscsi --op show --mode target
tgt-admin --dump

# THIS DOES NOT WORK (with SELinux) because VRTS and SElinux don't play well together (yet?)

vxassist -g dg_USS make lv_iSCSI 500G layout=mirror alloc="dg_USS01 dg_USS02"
mkfs.vxfs /dev/vx/dsk/dg_USS/lv_iSCSI
echo "/dev/vx/dsk/dg_USS/lv_iSCSI /var/lib/tgtd vxfs _netdev,defaults 0 0" >> /etc/fstab
mount /var/lib/tgtd


Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.