Comments on Using iSCSI On Debian Squeeze (Initiator And Target)

Using iSCSI On Debian Squeeze (Initiator And Target) This guide explains how you can set up an iSCSI target and an iSCSI initiator (client), both running Debian Squeeze. The iSCSI protocol is a storage area network (SAN) protocol which allows iSCSI initiators to use storage devices on the (remote) iSCSI target using normal ethernet cabling. To the iSCSI initiator, the remote storage looks like a normal, locally-attached hard drive.

3 Comment(s)

Add comment

Please register in our forum first to comment.

Comments

By: Anonymous

1. No need to install iscsitarget-dkms, honestly it is much better to use just iscsitarget and iscsitarget-modules

2. Adding a new device requires editing ietd.conf and "/etc/init.d/iscsitarget restart". Guess what happens to the clients :-)?

3. Not funny! They will loose their disks, broken fs and read-only.

 

There is an online way, just an quick example:

ietadm --op new --tid=$TID --lun=0 --params Path="/dev/vg_ssd/$LV_NAME"
ietadm --op new --tid=$TID --params Name='iqn.2009-05.cz.panelnet:storage.tukan.'$LV_NAME
 

Check your TIDs here

cat /proc/net/iet/volume

By: Ivan Zerlotti

In the case could help somebody.

In my case open-iscsi was already installed in the system and starting the service thrown the error message

Starting iSCSI initiator service: iscsid
Error: /etc/iscsi/initiatorname.iscsi does not contain a valid InitiatorName.
The iSCSI driver has not been correctly installed and cannot start.

 My workaround was writing

GenerateName=yes

in the first line of the file

/etc/iscsi/initiatorname.iscsi

Then restarting the service everything was fine.

 

By: emnwofw

Thanks a lot for post. I was getting errors like this (in dmesg):

[  672.791059] scsi host9: iSCSI Initiator over TCP/IP[  672.791487] iscsi: invalid can_queue of 8. can_queue must be a power of two that is at least 16.

I have to edit file

vim /etc/iscsi/nodes/iqn.2017-07.asdf\:temporaryDisk0/192.168.9.232\,3260\,1/default

and set line:

node.session.cmds_max = 16

There was 8. It should be higher. Both systems I have ubuntu 16.04 (server is server edition and client is standard ubuntu upgraded from older lts).

 

Thanks to this post I have found, where is that settings. Thanks.