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 08:55:52 +0200 [thread overview]
Message-ID: <06cf01c81153$eca36c70$0a00a8c0@ALDI2> (raw)
In-Reply-To: 20071018061907.GA22562@pentland.suse.de
[-- Attachment #1.1: Type: text/plain, Size: 1955 bytes --]
Hannes,
so is this behavior by design? In this case, patching in the scsi subsystem won't help to much, will it?
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?
Thanks
(Gerald)
----- Original Message -----
From: Hannes Reinecke
To: device-mapper development
Sent: Thursday, October 18, 2007 8:19 AM
Subject: Re: [dm-devel] multibus / failover and EMC CX600
On Wed, Oct 17, 2007 at 08:04:12PM +0200, Gerald Nowitzky wrote:
> I'm afraid the patch did not work for me. I'ts still the same.
>
> I am using kernel 2.6.22.2 at the moment. Should I upgrade to 2.6.23 ?
>
> Anybody any Ideas?
> The system is not in production at the moment. We could do some testing.
>
Well, yes. By the looks of if the problem is with multipathing still holding
references to the stale devices.
IE after dev_loss_tmo kicks in, the devices are removed from sysfs.
But multipathing does _not_ update it's device-mapper tables (that's why
you see all the '#' in the output), so there's still a refence on the
removed device and the in-kernel resources can't be freed.
So when the device is re-registered, you're getting this Oops.
Try to update the multipath information by running 'multipath' after the
devices have been removed. Once the '#' in the output are gone, you can
savely re-add the devices.
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: 3505 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-10-18 6:55 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 [this message]
2007-10-18 7:12 ` Hannes Reinecke
2007-10-18 8:07 ` Gerald Nowitzky
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='06cf01c81153$eca36c70$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.