From: James Smart <James.Smart@Emulex.Com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Problems with multipathing
Date: Tue, 18 Apr 2006 15:24:34 -0400 [thread overview]
Message-ID: <44453CF2.9080507@emulex.com> (raw)
In-Reply-To: <4443635F.5000401@free.fr>
Christophe Varoqui wrote:
> Do failover device nodes get reassigned during the rescan ?
> Like, for example, a configured path sda gets removed and a new path sdb
> appears ?
> If so, the FC transport class is in charge of the timeout triggering the
> dead devices removal.
> A hardware handler wouldn't help here.
On the kernel rev he's talking about, 2.6.9-34, the FC transport class
doesn't fully exist, so there's no automatic device removal.
-- james
prev parent reply other threads:[~2006-04-18 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 18:10 Problems with multipathing Roger Håkansson
2006-04-11 18:42 ` Christophe Varoqui
2006-04-11 21:04 ` Roger Håkansson
2006-04-13 17:14 ` Roger Håkansson
2006-04-13 20:48 ` Christophe Varoqui
2006-04-16 22:44 ` Roger Håkansson
2006-04-17 0:35 ` Roger Håkansson
2006-04-17 9:43 ` Christophe Varoqui
2006-04-17 14:17 ` Roger Håkansson
2006-04-18 4:47 ` Christophe Varoqui
2006-04-18 5:04 ` Roger Håkansson
2006-04-18 19:38 ` James Smart
2006-04-18 19:24 ` James Smart [this message]
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=44453CF2.9080507@emulex.com \
--to=james.smart@emulex.com \
--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.