I changed timeout as follows.
1. iscsiadm --mode discovery --type sendtargets --portal 192.168.7.174
2. iscsiadm -m node -T iqn.2008-05.com.abcde:Tar1 -p
192.168.7.174:3260 --login
3. iscsiadm -m node -T iqn.2008-05.com.qualexsystems:Tar1 -p
192.168.7.174:3260 -o update -n
On Sun, May 18, 2008 at 06:21:17PM -0700, Bryan Mclellan wrote:
Of the linux servers console? Sure I can dig one up, it's the first two lines
of the scsi disk sort of display, twice. Something sort of like:
Preferably the whole thing from start. Not just the last X lines.
Disk: DELL
Hi all,
Further update on this topic:
Thanks once again :) - If I manage to find/assert it, I will surely
post back.
I tried to do an experiment to confirm the maximum number of available
targets and LUNs with an initiator. I did:
On the target machine:
1. I created softlinks for a device
Stefan de Konink wrote:
What was the reason for adding the block device name to the block symlink
if this symlink already provides this name?
iscsi has not control over the block device naming and symlinks. You
would want to ask lkml.
It probably breaks everything that uses this block path
Shrey wrote:
Hi all,
Further update on this topic:
Thanks once again :) - If I manage to find/assert it, I will surely
post back.
I tried to do an experiment to confirm the maximum number of available
targets and LUNs with an initiator. I did:
On the target machine:
1. I created
