Of the packages you mention tgt is the only one which is iscsi target related.
I am looking at targetcli because my situation matches that of this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865632 That tells me what to migrate to, but the examples for usage of targetcli do not show working with existing iSCSI set up, only creating new, which would likely destroy my existing data. In the bug report it states: As the LIO stack was developed independently of the IET, the configuration has to be migrated manually. It doesn't say "you will lose your data", and it doesn't say "here is how to switch". I don't understand the inner workings of it. I guess in a worse case I can try to downgrade to Debian 8 with the older kernel and use iscsitarget again. On Mon, Jul 30, 2018 at 4:11 PM, Zen Boy <krus...@gmail.com> wrote: > I have an iscsi setup in Debian 9. I don’t think iscsitarget is a > supported package anymore? Do you have tgt, open-iscsi, lvm2 installed? > > Get Outlook for iOS <https://aka.ms/o0ukef> > > > > On Mon, Jul 30, 2018 at 2:54 PM -0400, "francis picabia" < > fpica...@gmail.com> wrote: > > This is with Debian 9 system which had been upgraded from Debian >> 8 a month or so ago. >> >> I have an existing iscsi target blockio device with /dev/md1 >> Somehow it continued working under Debian 9 until a recent reboot >> introduced a kernel update and then the module wasn't found: >> >> FATAL: Module iscsi_trgt not found in directory /lib/modules/4.9.0-7-amd64 >> >> The solution in the bug report about that is to switch to targetcli-fb >> >> When I look at the docs for targetcli, I don't see any hints/guides on >> how to configure >> an existing iSCSI target made before on the blockio device. >> >> My google fu has failed to find a guide/hints on existing iSCSI device >> conversion to targetcli. >> >> Does anyone have a hint or link to share? >> >> I have an existing target with valuable data on /dev/md1 and I need to >> configure it with targetcli. >> >> >>
