On Thursday, January 29, 2015 11:28:56 AM thegeezer wrote: > On 29/01/15 10:25, J. Roeleveld wrote: > > Hi all, > > > > I want to set up an iSCSI server (target in iSCSI terminology) running on > > Gentoo. > > Does anyone know which of the following 2 are better: > > - sys-block/iscsitarget > > - sys-block/targetcli > > > > Both don't seem to have had an update for over 2 years, but targetcli > > seems to be just the config-tool for whatever is in current kernels > > where, I think, iscsitarget is a userspace daemon? > > > > Many thanks, > > > > Joost > > I'd actually suggest using SCST > http://monklinux.blogspot.ie/2012/02/scst-configuration-how-to-using-gentoo. > html > > works very well and has a few extra niceties (dynamic resize > notification being one) that seem to be missing on other iscsi targets. > nice and easy syntax too
I managed to get dynamic resizing working when I did my first tests with targetcli and the kernel-inbuild stuff: Device Drivers ---> <M> Generic Target Core Mod (TCM) and ConfigFS Infrastructure ---> <M> TCM/IBLOCK Subsystem Plugin for Linux/BLOCK <M> TCM/FILEIO Subsystem Plugin for Linux/VFS <M> TCM/pSCSI Subsystem Plugin for Linux/SCSI <M> Linux-iSCSI.org iSCSI Target Mode Stack I only had to tell the iscsi-client to recheck the new size: server : # resize filesystem (Server was using targetcli with the kernel-inbuild stuff) client : # iscsiadm -m node -T iqn....vm5... -R client : # resize2fs /dev/sdb What is the difference between the kernel-stuff (targetcli is only the config- tool) and scst? -- Joost
