From: Tore Anderson <tore@linpro.no>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: CLARiiON failover modes and DM.
Date: Wed, 21 Nov 2007 08:20:50 +0100 [thread overview]
Message-ID: <4743DC52.8050809@linpro.no> (raw)
In-Reply-To: <940B4FF1F5958E4F96FC83C055A2F2611B8C84@exch-2003.incipient.waltham>
* Paul Cote
> Thanks for all the info ... Setting the CX FO mode to 1 appears to
> have clear up the mess. One thing I've noticed after doing a dynamic
> discovery of newly provisioned CX LUNs in that path state is
> generally wrong. It will come up as [active][faulty]and to correct
> that requires a reboot of the server. Don't know if that's a bug or
> not ... But I'm not opposed to a reboot.
That's odd, never had that problem myself. I rescan like this:
(where hostN is a FC adapter, repeat for all of them but give it some
time between iterations as you'll see paths failing for a short while):
echo 1 > /sys/class/fc_host/hostN/issue_lip
echo - - - > /sys/class/scsi_host/hostN/scan
Usually only these steps are required to discover new volumes properly,
but you can also force a rediscovery of the multipath topology and maybe
also do a restart of multipathd:
multipath -v2
pkill multipathd && multipathd
Regards
--
Tore Anderson
next prev parent reply other threads:[~2007-11-21 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 16:14 CLARiiON failover modes and DM Paul Cote
2007-11-19 18:51 ` Tore Anderson
2007-11-19 20:20 ` Paul Cote
2007-11-20 7:46 ` Tore Anderson
2007-11-20 18:59 ` Paul Cote
2007-11-21 7:20 ` Tore Anderson [this message]
2007-11-20 11:20 ` Stephan Austermühle
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=4743DC52.8050809@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.