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?
----- Original Message -----
Sent: Thursday, October 18, 2007 8:19
Subject: Re: [dm-devel] multibus /
failover and EMC CX600
On Wed, Oct 17, 2007 at 08:04:12PM +0200, Gerald
> I'm afraid the patch did not work for me. I'ts still
> I am using kernel 18.104.22.168 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.
yes. By the looks of if the problem is with multipathing still
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
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
Dr. Hannes Reinecke
zSeries & Storage
hare suse de +49
911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nrnberg
Markus Rex, HRB 16746 (AG Nrnberg)
dm-devel mailing list
dm-devel redhat com