Sean S sstra...@gmail.com schrieb am 13.07.2010 um 20:41 in Nachricht
1f2389e7-9717-4f82-a05c-671f36a4c...@x21g2000yqa.googlegroups.com:
I'm running an iscsi root partition for a CentOS machine running a
2.6.18-53 kernel. Every couple of days I get the error:
connection1:0 detected conn
Mike michaelaush...@gmail.com schrieb am 13.07.2010 um 16:08 in Nachricht
920d464c-9a0c-462c-9d33-37a967be8...@r27g2000yqb.googlegroups.com:
Hi Mike,
Thank you for the quick reply. I have 2 questions if you don't mind
clarifying for me:
1) Is the logout option what disconnects the
Sean S sstra...@gmail.com schrieb am 14.07.2010 um 04:33 in Nachricht
83cd8c40-2e84-4c52-a864-36643dd0a...@d8g2000yqf.googlegroups.com:
Nothing else in the log from iscsid. No mention of a failed reconnect,
although the only log I'm really able to access post failure is dmesg.
Since I'm
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
Mike Christie wrote:
It should retry the login forever. If that does not work on RHEL 5.4 let me
know.
Mike,
My mistake, it tries also after the recovery (replacement timeout) passed
and I guess for ever.
Or.
--
You received this message because you are subscribed to the Google Groups
On 07/14/2010 03:59 AM, Ulrich Windl wrote:
Sean Ssstra...@gmail.com schrieb am 13.07.2010 um 20:41 in Nachricht
1f2389e7-9717-4f82-a05c-671f36a4c...@x21g2000yqa.googlegroups.com:
I'm running an iscsi root partition for a CentOS machine running a
2.6.18-53 kernel. Every couple of days I get
On 07/14/2010 05:30 AM, HIMANSHU wrote:
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?
If you run
On 07/14/2010 08:20 AM, Mike wrote:
Hi Mike/Ulrich,
Thank you for your input.
Mike, sorry I'm very new to all this so I apologize for not understand
what you said above. Where/How do I allow access for the initiator?
I am not sure. What target are you using? You normally configure this on
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 of iscsiadm commands like
discovery,login,logout.
I think,all of them directly returns
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 of iscsiadm commands like
Hi Mike,
Yes, that is correct. The machine I cloned works perfectly with iSCSI
setup. I can ping the IP but just not able to discover it.
Thank you,
Mike
On Jul 14, 10:57 am, Mike Christie micha...@cs.wisc.edu wrote:
On 07/14/2010 08:20 AM, Mike wrote:
Hi Mike/Ulrich,
Thank you for your
What's the relevance of /var/lib/iscsi/static?
I'm going to make an assumption an say that's where we can define
static(permanent) target volumes that do not require discovery and
will automatically logged in at boot?
--
You received this message because you are subscribed to the Google Groups
Thanks for replies.
Yes,I generally do it using $? for other linux commands,but somehow
not comfortable doing it here.
iscsiadm -m ... sucess 2failure
and if file is non-empty,print the contents accordingly is what I can
think of.
It might be very ugly way of doing it.
On Jul 14, 2:20 pm, Mike
13 matches
Mail list logo
