All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Clariion CX600 automatic failback support
Date: Fri, 4 Nov 2005 10:47:51 +0100	[thread overview]
Message-ID: <20051104094751.GB9826@free.fr> (raw)
In-Reply-To: <200511040919.07200.bernd@bzed.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1298 bytes --]

On Fri, Nov 04, 2005 at 09:19:06AM +0100, Bernd Zeimetz wrote:
> Hi,
> 
> > Looks good, except the call to extract_hwe_from_path in setup_multipath
> > must be before the call to select_pgfailback.
> >
> 
> We have a ton of these log messages now.
> >From the last about 2 hours:
> 
> 580x multipathd: 3600601f4a20c000099dc229956b0d711: switch to path group #1
> 714x multipathd: 3600601f4a20c000096dc229956b0d711: switch to path group #1
> 714x multipathd: 3600601f2a20c0000fb13caa656b0d711: switch to path group #1
>   45x kernel: device-mapper: dm-emc: emc_pg_init: sending switch-over command
> 
> It happens only for these 3 of 8 luns.
> 
> Kernel is 2.6.13.4, devmapper 1.01, latest multipath-tools from git, evms 
> 2.5.3
> 
> zeus-1:/# cat /etc/multipath.conf
> defaults {
>         failback                                immediate
> }
> 
> 
> Since we had a lot of trouble with our CX400 (Hardware problems, but they're 
> supposed to be fixed) I'm wondering what these messages mean, and if we still 
> have hardware/software bugs somewhere.
> 
Yes, the test to determine if a switch is needed is sub-optimal :
The no activated PG case (all Enabled for exampleÃ) keeps triggering a switch.
I checked-in a patch to solve that issue.

Regards,
cvaroqui

  reply	other threads:[~2005-11-04  9:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 18:16 Clariion CX600 automatic failback support goggin, edward
2005-11-03 20:55 ` Brian Long
2005-11-03 22:00   ` Bernd Zeimetz
2005-11-04  8:19 ` Bernd Zeimetz
2005-11-04  9:47   ` Christophe Varoqui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-06 18:29 goggin, edward
2005-11-04 19:36 goggin, edward
2005-11-04 20:55 ` Christophe Varoqui
2005-11-05  0:03   ` Bernd Zeimetz
2005-11-05 12:26     ` Christophe Varoqui
2005-11-10 19:24       ` Bernd Zeimetz
2005-11-02 21:32 goggin, edward
2005-11-03 13:58 ` Christophe Varoqui
2005-11-07 19:25 ` Benjamin Marzinski
2005-10-26 19:37 Phil Lowden (plowden)
2005-10-31 13:58 ` Brian Long
2005-10-31 14:02   ` Bernd Zeimetz
2005-10-31 14:07   ` Christophe Varoqui
2005-10-31 15:51     ` Brian Long
2005-10-31 16:06       ` Christophe Varoqui

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=20051104094751.GB9826@free.fr \
    --to=christophe.varoqui@free.fr \
    --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.