<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hannes,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>so is this behavior by design? In this case,
patching in the scsi subsystem won't help to much, will it?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>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?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thanks</FONT></DIV>
<DIV><FONT face=Arial size=2>(Gerald)</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=hare@suse.de href="mailto:hare@suse.de">Hannes Reinecke</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=dm-devel@redhat.com
href="mailto:dm-devel@redhat.com">device-mapper development</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, October 18, 2007 8:19
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [dm-devel] multibus /
failover and EMC CX600</DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial
size=2></FONT><BR></DIV>On Wed, Oct 17, 2007 at 08:04:12PM +0200, Gerald
Nowitzky wrote:<BR>> I'm afraid the patch did not work for me. I'ts still
the same.<BR>> <BR>> I am using kernel 2.6.22.2 at the moment. Should I
upgrade to 2.6.23 ?<BR>> <BR>> Anybody any Ideas?<BR>> The system is
not in production at the moment. We could do some testing.<BR>> <BR>Well,
yes. By the looks of if the problem is with multipathing still
holding<BR>references to the stale devices.<BR>IE after dev_loss_tmo kicks in,
the devices are removed from sysfs.<BR>But multipathing does _not_ update it's
device-mapper tables (that's why<BR>you see all the '#' in the output), so
there's still a refence on the<BR>removed device and the in-kernel resources
can't be freed.<BR><BR>So when the device is re-registered, you're getting
this Oops.<BR><BR>Try to update the multipath information by running
'multipath' after the<BR>devices have been removed. Once the '#' in the output
are gone, you can<BR>savely re-add the
devices.<BR><BR>Cheers,<BR><BR>Hannes<BR>-- <BR>Dr. Hannes Reinecke
zSeries & Storage<BR><A
href="mailto:hare@suse.de">hare@suse.de</A> +49
911 74053 688<BR>SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nrnberg<BR>GF:
Markus Rex, HRB 16746 (AG Nrnberg)<BR><BR>--<BR>dm-devel mailing list<BR><A
href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</A><BR><A
href="https://www.redhat.com/mailman/listinfo/dm-devel">https://www.redhat.com/mailman/listinfo/dm-devel</A></BLOCKQUOTE></BODY></HTML>