From: "Gerald Nowitzky" <Nowitzky@igne.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: multibus / failover and EMC CX600
Date: Thu, 18 Oct 2007 10:07:59 +0200 [thread overview]
Message-ID: <06e001c8115d$ffd7e9b0$0a00a8c0@ALDI2> (raw)
In-Reply-To: 20071018071244.GB22562@pentland.suse.de
[-- Attachment #1.1: Type: text/plain, Size: 2163 bytes --]
Hannes,
nothing that looks really bedrohlich in the syslog.
What I have done:
9:47 multipathd -v 6 started
9:50 2:0:0:0 and 1:0:1:0 blocked (both paths to SP-A of the SAN)
9:52 2:0:0:0 and 1:0:1:0 re-enabled
I have attached my syslog.
I am on a gentoo with multipath 0.4.7
(Gerald)
----- Original Message -----
From: Hannes Reinecke
To: device-mapper development
Sent: Thursday, October 18, 2007 9:12 AM
Subject: Re: [dm-devel] multibus / failover and EMC CX600
On Thu, Oct 18, 2007 at 08:55:52AM +0200, Gerald Nowitzky wrote:
> Hannes,
>
> so is this behavior by design? In this case, patching in the scsi subsystem won't
> help to much, will it?
>
No, not really.
> Manually updating the multipath information - well, yes, that will work I guess,
> but in the end that should work without manual intervention. Thus, I'd need to have
> a job checking the multipath table if there are stale devices, and, if there are,
> rerun multipath to get them out. Not exactly smooth, is it?
>
Why, we do have interns for this kind of work :-)
No, really: Normally this should be done by multipathd / udev. With the mainline
multipathd it reads from the kernel netlink socket and will get a uevent if
a device is removed. And it should update the tables accordingly.
There have been problems with device-mapper itself (older versions required to
flush all outstanding I/O before the table could be modified), but that should
be resolved by now.
So maybe have multipathd running in verbose mode (ie -v 6 or somesuch) and see
what's going on. Especially why it isn't updating the device-mapper tables.
BTW, which distribution are you running? multipath & udev seem to be a tricky
area for most.
Not ours, of course :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nrnberg
GF: Markus Rex, HRB 16746 (AG Nrnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
[-- Attachment #1.2: Type: text/html, Size: 3992 bytes --]
[-- Attachment #2: syslog.zip --]
[-- Type: application/x-zip-compressed, Size: 7679 bytes --]
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-10-18 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 10:23 multibus / failover and EMC CX600 Gerald Nowitzky
2007-10-17 10:40 ` Tore Anderson
2007-10-17 11:08 ` Hannes Reinecke
2007-10-17 12:32 ` Tore Anderson
2007-10-17 14:48 ` Gerald Nowitzky
2007-10-17 16:01 ` Tore Anderson
2007-10-17 18:04 ` Gerald Nowitzky
2007-10-18 6:19 ` Hannes Reinecke
2007-10-18 6:55 ` Gerald Nowitzky
2007-10-18 7:12 ` Hannes Reinecke
2007-10-18 8:07 ` Gerald Nowitzky [this message]
2007-10-19 22:35 ` David Strand
2007-10-17 19:38 ` Gerald Nowitzky
2007-10-18 6:01 ` Tore Anderson
2007-10-18 6:19 ` Tore Anderson
2007-10-17 19:49 ` Mike Christie
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='06e001c8115d$ffd7e9b0$0a00a8c0@ALDI2' \
--to=nowitzky@igne.de \
--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.