How can we know error status of iscsiadm commands like
discovery,login,logout.
I think,all of them directly returns corresponding success/failure
messages.
so mostly I can just fire the commands without checking any error
codes after it?
I will really appreciate any help.
Thank you.
--
You
Christie micha...@cs.wisc.edu wrote:
On 07/14/2010 12:56 PM, Boaz Harrosh wrote:
On 07/14/2010 08:23 PM, Mike Christie wrote:
On 07/14/2010 10:49 AM, Boaz Harrosh wrote:
On 07/14/2010 05:52 PM, Mike Christie wrote:
On 07/14/2010 05:30 AM, HIMANSHU wrote:
How can we know error status
Apr 2009 at 11:25, Mike Christie wrote:
Ulrich Windl wrote:
On 28 Apr 2009 at 7:10, HIMANSHU wrote:
One more question analogues to this.
Suppose I login to 1st target from machine 30.12,it was having node
authentication.so I saved its credentials in iscsid.conf and then I
.
So solution would be maintaining separate iscsid.conf files per logged
in target.Can I do that here?
ietd allows to read from different configuration file.right?
On Apr 28, 9:19 am, HIMANSHU makhu...@yahoo.co.in wrote:
Thank you very much Mike for all this.
Can you please give me the test src rpm
Thank you very much Mike for all this.
Can you please give me the test src rpm for CentOS 5.4?
On Apr 27, 8:50 pm, Mike Christie micha...@cs.wisc.edu wrote:
HIMANSHU wrote:
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still
target configuration changes on the
target side in this whole process.Just discovery followed by
'node.startup update to automatic command'.and again performing
discovery causes overwriting.
Am I going wrong somewhere in the steps?
Thanks and Regards,
Himanshu Padmanabhi.
On Apr 22, 6:38 pm, Mike
Is there any method or should I debug to know the exact cause of this
overwriting problem?
On Apr 24, 6:29 pm, HIMANSHU makhu...@yahoo.co.in wrote:
I am now having 'iscsi-initiator-utils-6.2.0.868-0.18.el5' and
performed the steps mentioned in my last post.
Still after when I discover using
Thank you very much all.Problem is solved,but I am having doubt.
@Mike
On Apr 21, 5:08 am, Mike Christie micha...@cs.wisc.edu wrote:
HIMANSHU wrote:
I discovered 2 machine,192.168.7.50(containing 10 targets,out of which
performed login on 2) and 192.168.7.51(containing 5 targets,out
I discovered 2 machine,192.168.7.50(containing 10 targets,out of which
performed login on 2) and 192.168.7.51(containing 5 targets,out of
which performed login on 3).I am using IET target and 'iscsi-initiator-
utils-6.2.0.868-0.7.el5' initiator.
So at present there are 5 connections on
This is related to my this post.
http://groups.google.com/group/open-iscsi/browse_thread/thread/40166b414bbda322/66ff12bbb
I want to confirm my observations.If I am wrong,forgive me.
Can I delete nodes and sendtargets once the discovery and login
are done with 'target' from 'targetmachine1'?
:
HIMANSHU wrote:
Hi all,
I am asking very basic,simple question here.I am using iscsi-
initiator-utils-6.2.0.865-0.2.fc7.
iscsiadm -m discovery -t sendtargets -p ip:port
It says that ip:port should be specified.It worked with 'machine
name' stead of 'ip' also.
This works
Hi all,
I am asking very basic,simple question here.I am using iscsi-
initiator-utils-6.2.0.865-0.2.fc7.
iscsiadm -m discovery -t sendtargets -p ip:port
It says that ip:port should be specified.It worked with 'machine
name' stead of 'ip' also.
iscsiadm -m node -T targetname -p ip:port --login
IET target is connected by MS initiator.Data transfer is going on on
the connected disk on initiator.
TCP connection failed(because of any reason,service failure,problems
in kernel modules) at say 't1' second.Initiator kept trying for
reconnect.
Initiator actually recognizes that target is
Hi all,
This is the surprising scenario.
I created a VG containing one local and one remote(iSCSI) disk taken
from target.Then I created 2-3 LV's with file system on it and filled
them all with some data till they become full.Then I removed remote
disk i.e. perform logout operation of iSCSI
I am sure I mailed to the right list..:)
On Aug 29, 5:16 pm, HIMANSHU [EMAIL PROTECTED] wrote:
I am using iscsi-initiator-utils-6.2.0.865-0.2.fc7 and
iscsitarget-0.4.15-1 on CentOS5.
CHAP says it adds Bidirectional authentication just to add a second
level of security in which initiator
I am using iscsi-initiator-utils-6.2.0.865-0.2.fc7 and
iscsitarget-0.4.15-1 on CentOS5.
CHAP says it adds Bidirectional authentication just to add a second
level of security in which initiator authenticates the target.
Even though target specified Bi-Directional Credentials,Initiator
can login
Hello,
You need iscsi-initiator-utils-6.2.0.version for using iscsiadm
commands.
On Jul 17, 1:38 pm, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
I am trying to install open-iscsi package in the suse linux. But I am
facing some problem while installation.
When we complete this installation do
Let me take this a chunk at a time :)
HIMANSHU wrote:
My previous problem that initiator cannot recover the connection after
target daemon restart/target machine
Hello,
First of all,Thanks Mike for your continuous help.
You are really making this list active.
---
Consider the scenario,
Open-iSCSI initiator connected to one
Detailed results are mailed to you mike.It is an excel table.I
couldn't paste it here.
Vaguely,We could conclude that if CRC32C was there @ iscsid.conf,it
was unable to recover the connection.Disks show blocked for many
time after which they become running but iSCSI connection state
remains
# ietadm --op show --tid=1
Wthreads=8
Type=0
QueuedCommands=32
On Jun 28, 5:46 pm, HIMANSHU [EMAIL PROTECTED] wrote:
I am having Wthreads 8 in my IET /etc/ietd.conf
So after restarting target module and daemon,Initiator failed to
connect to it due to absense of Wthreads.
How to specify
Hi I switched to iscsi-initiator-utils-6.2.0.868-0.7.fc9 from iscsi-
initiator-utils-6.2.0.865-0.2.fc7.
Facing problem at discovery.
# iscsiadm -d 8 --mode discovery --type sendtargets --portal
192.168.7.174:3260
iscsiadm: ip 192.168.7.174, port 3260, tgpt -1
iscsiadm: Max file limits 1024
If lun is having LV(i.e.Virtual Block device) in it,then it should be
exposed as Blockio.
If it is exposing Regular file,then it should use Fileio.
Is it right?
Regular file is exposed as a disk.What is difference between 'Blockio
and Fileio in iSCSI.
Hi Vaibhav,
I am facing similar problem after restart that Disks on the initiator
side becomes inaccessible.
Which service are you restarting? iscsi-target service?
Did you modified it?
Probably on sensing iscsi-target restart on initiator side,you might
be relogging to it.
At that time,it might
Hello...
1. Initiator is using one disk,Creates VG,LV on it.automounts
LV.
But these VG,LV become visible(accessible) on the target side
also...
This is not desirable feature.Right?...Any
solution??
M using IET 16.1 and
1.
You say that performance figures are this..
single iSCSI session:
* 450MB/s Read and 450 MB/s Write for 64KB block
* 510 MB/s Read and 550 MB/s Write for 256KB block
* 65,000 IOPS - 1K, 58,000 IOPS - 2K, 50,000 IOPS with 4KB Read
two iSCSI sessions:
* 550 MB/s Read and 810
Currently iSCSI targets contains LV's.
--
Target iqn.2008-06.com.qualexsystems:Tar3
Alias Tar3
#instead of adding LV here,regular file should be added.
Lun 0 Path=/dev/Vg1/lvISCSI3,Type=fileio
HeaderDigest CRC32C,None
InitialR2T Yes
Suppose Initiator is logged in to a Disk,It created File System on
it.Then after mounting,written some data in it.
After this,Initiator logged out that target.If it Again logged in to
same target,all previously written data was accessible.
This is normal and expected behavior.I want same
Hi,
1.To discover targets,
iscsiadm --mode discovery --type sendtargets --portal 'target_ip'
2.For login,
iscsiadm -m node -T 'target_name' -p 'target_ip':3260 --login
3. Use exported disk on initiator(create PV,LV,use that LV etc.)
4. For logout,
iscsiadm -m node -T 'target_name' -p
Thanks a lot Konrad and Mike for your continuous help.
@Konrad
Sorry, I meant to say If I/O going on,it shouldn't be allowed to
logout that target.
Suppose I added few targets and want initiators should know this
change,i should restart iscsi-target daemon.Without this,iscsiadm -
m
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
I) How to increase replacement_timeout on initiator?
echo 82400 /sys/block/sdh/device/timeout
or
After discovery,nodes sendtargets are created.In nodes,there is
default file.
node.session.timeo.replacement_timeout = 120
node.session.err_timeo.abort_timeout = 10
Hello All,
1. I am using latest iscsitarget-0.4.16-1 from sourceforge.
Now,can you tell whether it is expected to retain the connection with
initiator once the target is restarted?
-
2. You wrote.
The reason for having you do
33 matches
Mail list logo
