2018-02-18 01:53 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001756openmediavaultBugpublic2018-02-12 16:39
Assigned Tovotdev 
Product VersionErasmus (3.x) 
Target VersionFixed in Version 
Summary0001756: Replace iscsitarget with something still maintained
Descriptioniscsitarget does not appear to be maintained since 2014, and the packages are not even available in newer versions of debian.

The current Jessie/Erasmus iscsitarget-dkms module will not compile with backport kernels (currently 4.9.0). So I am left with a choice between iscsi or reliable (storage) HW support... (3.16.0 is not usable)

I note Jessie has two other iscsi target options:
 * tgt - Userspace tools for the already mainlined iscsi_target_mod.ko
 * istgt - An entirely userspace server from the BSD world

Could openmediavault-iscsitarget (3.x) be made to output config files for one of these?

(I saw another ticket here suggesting LIO, but I could not find something like that with apt-cache search)
Steps To ReproduceWith Jessie-backports enabled:

apt-get -t jessie-backports install linux-image-amd64 linux-headers-amd64
apt-get install openmediavault-iscsitarget
(iscsitarget-dkms install will fail)
Additional InformationHow could I get this prioritised for OMV 3.x ?
TagsNo tags attached.
Product build3.0.77
Attached Files




DisasteR42 (reporter)



Lio will be a better choice.


jaendlingt (reporter)

Not sure that is true for Debian:


^ targetcli not available in an Debian release, not any version used by OMV



^ tgt available in all Debian releases.

Also: I've already switch to tgt on a number of our OMV servers, and it has proved to be for more stable/reliable that the old iscsitarget.

I can also that it was rather easy to configure via the cli; and I really like that the kernel module is mainlined.

Initiators in our Env. are ESXi servers and Windows servers.


ryecoaaron27 (reporter)

I haven't used tgt. Is the setup similar to iscsitarget?


tom1gozzi (reporter)

Hi, jaendlingt,

thank you very much about:

Also: I've already switch to tgt on a number of our OMV servers, and it has proved to be for more stable/reliable that the old iscsitarget.

I'm in use too ESXi and Windows servers, and i will be very happy to knew more of yours experiments with these parts.

How difficult was installs tgt to makes available in OMV ?

Or whatever sorts of experiences you gave, i guess, these will be very very so wellcome i thing for the multitude...



jaendlingt (reporter)

Obviously you cannot use the WebUI, that what this ticket is for, so you have to ssh in. Once tgt is installed, here some examples on configuring Targets and LUNs:

## Create new target with tid 1
tgtadm --lld iscsi --mode target --op new --tid=1 --targetname 'iqn.201x-yy.com.exmaple.my.system:label1'

## Add LUN to taget
tgtadm --lld iscsi --mode logicalunit --op new --tid 1 --lun 1 -b /dev/mapper/vgData-lvLabel1

## Check all is ok
tgt-admin -s

## Bind target and present it
tgtadm --lld iscsi --mode target --op bind --tid 1 -I 172.aa.bb.cc/dd

## Check and save new config (to survive reboot)
tgt-admin --dump
tgt-admin --dump >/etc/tgt/conf.d/local.conf

#Creating a target with two LUNs
tgtadm --lld iscsi --mode target --op new --tid=2 --targetname 'iqn.201x-yy.com.example.my.system:esxi'
tgtadm --lld iscsi --mode logicalunit --op new --tid 2 --lun 1 -b /dev/mapper/vgData-lvEsxi
tgtadm --lld iscsi --mode logicalunit --op new --tid 2 --lun 2 -b /dev/mapper/vgTest-lvTest
tgt-admin -s
tgtadm --lld iscsi --mode target --op bind --tid 2 -I 172.aa.bb.cc/dd
tgt-admin --dump
tgt-admin --dump >/etc/tgt/conf.d/local.conf

# Just for info, what /etc/tgt/conf.d/local.conf look like (created by tgt-admin --dump above)
# cat /etc/tgt/conf.d/local.conf
default-driver iscsi

<target iqn.201x-yy.com.exmaple.my.system:label1>
        backing-store /dev/mapper/vgData-lvLabel1
        initiator-address 172.aa.bb.cc/dd

<target iqn.201x-yy.com.example.my.system:esxi>
        backing-store /dev/mapper/vgData-lvEsxi
        backing-store /dev/mapper/vgTest-lvTest
        initiator-address 172.aa.bb.cc/dd

-Issue History
Date Modified Username Field Change
2017-06-05 16:18 jaendlingt New Issue
2017-06-05 16:18 jaendlingt Status new => assigned
2017-06-05 16:18 jaendlingt Assigned To => votdev
2017-06-28 19:55 DisasteR42 Note Added: 0004821
2017-06-29 07:46 jaendlingt Note Added: 0004822
2017-06-30 15:03 ryecoaaron27 Note Added: 0004823
2018-02-12 14:20 tom1gozzi Note Added: 0005134
2018-02-12 16:39 jaendlingt Note Added: 0005138
+Issue History