From: Eli Stair <estair@ilm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Failover between two paths to one LU doesn't work onlinux-iscsi
Date: Tue, 10 Oct 2006 10:24:56 -0700 [thread overview]
Message-ID: <452BD768.30206@ilm.com> (raw)
In-Reply-To: <452BD5C6.2080808@voltaire.com>
What versions of the tools and kernel are you running? What are your
settings for multipath.conf? Is multipathd running? If you run
multipath -v2 manually, does it fail the path? Etc.
> 1. Are there any known problems that can cause fail-over not to happen
> in linux-iscsi?
> 2. Is there any way to get debug information in order to understand more
> in-depth what's going on?
man multipath && man multipathd
multipathd -d
multipath -v4
> 3. How can I know what the timeouts are and how to change them?
Timeouts occur at several levels. Your HBA or iSCSI driver will have
(at least) one. Check the documentation for the aspects of
software/hardware you're using (kernel module options), dm-multipath
docs, etc.
> 4. If you need more specific information, please write what can help.
http://christophe.varoqui.free.fr/wiki/wakka.php?wiki=Home
I've never done multipath-iscsi, so don't have direct experience. Try
posting some more detailed info on your setup and what errors or info
messages are occuring.
/eli
next prev parent reply other threads:[~2006-10-10 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 17:17 Failover between two paths to one LU doesn't work on linux-iscsi Michae Lyulko
2006-10-10 17:24 ` Eli Stair [this message]
2006-10-10 19:55 ` Failover between two paths to one LU doesn't work onlinux-iscsi Michae Lyulko
2006-10-11 14:16 ` Dave Wysochanski
2006-10-12 18:49 ` Michael Lyulko
2006-10-12 20:28 ` David Wysochanski
2006-10-18 18:55 ` Michael Lyulko
2006-11-01 6:20 ` Dave Wysochanski
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=452BD768.30206@ilm.com \
--to=estair@ilm.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.