Doron Shoham wrote:
If you promise to test me the script with the STP fixes I'll be willing
to add it. Sadly I don't have time currently to do any decent testing here,
but I'm always open to patches :-)
Cheers,
Hannes
Hi Hannes,
Unfortunately I don't have any setup which I could test
Hi Doron,
Doron Shoham wrote:
Actually this was bad. If we have to wait for the login_timeout to fire
then initial_login_retry_max = 4 was a nice round number and the max
time we had to wait was 1 minute. If I just increase it (tried 45
stupidly first), it increases the possible max default
Doron Shoham wrote:
Actually this was bad. If we have to wait for the login_timeout to fire
then initial_login_retry_max = 4 was a nice round number and the max
time we had to wait was 1 minute. If I just increase it (tried 45
stupidly first), it increases the possible max default wait to 11
Eli Dorfman wrote:
On Tue, Sep 23, 2008 at 8:04 PM, Mike Christie [EMAIL PROTECTED] wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which were
set
to automatic login?
To avoid deadlocks on the root fs there is patch which limits the number
Hannes Reinecke wrote:
On Tue, Sep 23, 2008 at 12:13:19PM -0500, Mike Christie wrote:
Hannes Reinecke wrote:
Hi Doron,
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which
were set
to automatic login?
To avoid deadlocks on
Mike Christie wrote:
Hannes Reinecke wrote:
On Tue, Sep 23, 2008 at 12:13:19PM -0500, Mike Christie wrote:
Hannes Reinecke wrote:
Hi Doron,
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which
were set
to automatic login?
Also, what is the purpose of node.startup parameter?
When is it in use?
Hi Mike,
Can you please explain this?
Thanks,
Doron
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which were set
to automatic login?
To avoid deadlocks on the root fs there is patch which limits the number of
retries on first login.
When doing so, it sets back all the default parameters
Hannes Reinecke wrote:
Hi Doron,
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which
were set
to automatic login?
To avoid deadlocks on the root fs there is patch which limits the
number of retries on first login.
When
Mike Christie wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which
were set
to automatic login?
To avoid deadlocks on the root fs there is patch which limits the
number of retries on first login.
When doing so, it sets back all the
Hi Doron,
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which were
set
to automatic login?
To avoid deadlocks on the root fs there is patch which limits the number of
retries on first login.
When doing so, it sets back all
On Mon, Sep 22, 2008 at 9:39 AM, Hannes Reinecke [EMAIL PROTECTED] wrote:
Hi Doron,
Doron Shoham wrote:
Doron Shoham wrote:
Hi,
Why does the init script on suse re-discovers all iscsi targets which were
set
to automatic login?
To avoid deadlocks on the root fs there is patch which
12 matches
Mail list logo
