From: seth vidal <skvidal@linux.duke.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: failover time and failback time
Date: Sat, 26 Aug 2006 14:06:56 -0400 [thread overview]
Message-ID: <1156615617.13298.25.camel@cutter> (raw)
In-Reply-To: <1156613723.13298.18.camel@cutter>
On Sat, 2006-08-26 at 13:35 -0400, seth vidal wrote:
> Hi,
<snip>
> Then I yank one connection on one of the cards in the back of the
> system.
> I watch dmesg and I see:
> qla2300 0000:03:0b.0: LOOP DOWN detected (2).
>
> At this point I would expect multipathd to fail out the paths connected
> and continue happily.
>
So, I think I know why multipathd was failing back correctly :)
It's because it wasn't running. I thought it was but I was wrong.
However, now I'm seeing this when it tries to failover:
Aug 26 14:04:10 multipathd: error calling out /sbin/mpath_prio_alua
8:240
Aug 26 14:04:10 kernel: SCSI error : <1 0 3 3> return code = 0x10000
I've checked /sbin/mpath_prio_alua works to run - so I'm not sure where
I should look next.
Thanks,
-sv
next prev parent reply other threads:[~2006-08-26 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 17:35 failover time and failback time seth vidal
2006-08-26 18:06 ` seth vidal [this message]
2006-08-26 18:39 ` seth vidal
2006-08-26 19:14 ` seth vidal
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=1156615617.13298.25.camel@cutter \
--to=skvidal@linux.duke.edu \
--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.