From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multibus / failover and EMC CX600
Date: Wed, 17 Oct 2007 14:32:55 +0200 [thread overview]
Message-ID: <471600F7.5090607@linpro.no> (raw)
In-Reply-To: <4715ED28.9020102@suse.de>
* Hannes Reinecke
> That's the dev_loss_tmo setting. Just increase it to something to
> your liking.
Oh, sweet. This knob won't affect how long the layer will hold I/O
before failing it (like lpfc_nodev_tmo), I assume? (I'm worried about
it taking longer for dm-multipath to detect failed paths).
I wish it could've been set to unlimited, though. Seems like there's
always some kind of trouble with re-adding the devices, either I run
into that -EEXIST bug, or udev doesn't do it's job properly and the
revived device isn't added back into the dm-multipath map. In addition
it somtimes breaks queue_if_no_path with earlier multipath-tools that
doesn't use no_flush on suspend. Those versions are of course included
in most server distributions... Sigh.
Regards
--
Tore Anderson
next prev parent reply other threads:[~2007-10-17 12:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 10:23 multibus / failover and EMC CX600 Gerald Nowitzky
2007-10-17 10:40 ` Tore Anderson
2007-10-17 11:08 ` Hannes Reinecke
2007-10-17 12:32 ` Tore Anderson [this message]
2007-10-17 14:48 ` Gerald Nowitzky
2007-10-17 16:01 ` Tore Anderson
2007-10-17 18:04 ` Gerald Nowitzky
2007-10-18 6:19 ` Hannes Reinecke
2007-10-18 6:55 ` Gerald Nowitzky
2007-10-18 7:12 ` Hannes Reinecke
2007-10-18 8:07 ` Gerald Nowitzky
2007-10-19 22:35 ` David Strand
2007-10-17 19:38 ` Gerald Nowitzky
2007-10-18 6:01 ` Tore Anderson
2007-10-18 6:19 ` Tore Anderson
2007-10-17 19:49 ` Mike Christie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=471600F7.5090607@linpro.no \
--to=tore@linpro.no \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.