<!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>not much difference with
2.6.23.1:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Oct 17 22:33:56 SANfile_m kernel: kobject_add
failed for 1:0:1:0 with -EEXIST, don't try to register things with<BR>the same
name in the same directory.<BR>Oct 17 22:33:56 SANfile_m kernel:
[<c03074d5>] kobject_shadow_add+0x115/0x1b0<BR>Oct 17 22:33:56 SANfile_m
kernel: [<c03a8f58>] device_add+0xa8/0x5a0<BR>Oct 17 22:33:56
SANfile_m kernel: [<c02fc582>]
__blk_queue_init_tags+0x32/0x70<BR>Oct 17 22:33:56 SANfile_m kernel:
[<c03fb8af>] scsi_sysfs_add_sdev+0x4f/0x220<BR>Oct 17 22:33:56 SANfile_m
kernel: [<f99498b7>] qla2xxx_slave_configure+0x77/0x110
[qla2xxx]<BR>Oct 17 22:33:56 SANfile_m kernel: [<c03f986a>]
scsi_probe_and_add_lun+0x92a/0x950<BR>Oct 17 22:33:56 SANfile_m kernel:
[<c03fa26d>] __scsi_scan_target+0x4fd/0x5b0<BR>Oct 17 22:33:56 SANfile_m
kernel: [<c03fa954>] scsi_scan_target+0x94/0xc0<BR>Oct 17 22:33:56
SANfile_m kernel: [<c04014f0>] fc_scsi_scan_rport+0x0/0x90<BR>Oct 17
22:33:56 SANfile_m kernel: [<c0401568>]
fc_scsi_scan_rport+0x78/0x90<BR>Oct 17 22:33:56 SANfile_m kernel:
[<c013e963>] run_workqueue+0x73/0x100<BR>Oct 17 22:33:56 SANfile_m
kernel: [<c0142350>] autoremove_wake_function+0x0/0x50<BR>Oct 17
22:33:56 SANfile_m kernel: [<c013f3dc>]
worker_thread+0x9c/0x100<BR>Oct 17 22:33:56 SANfile_m kernel:
[<c0142350>] autoremove_wake_function+0x0/0x50<BR>Oct 17 22:33:56
SANfile_m kernel: [<c013f340>] worker_thread+0x0/0x100<BR>Oct 17
22:33:56 SANfile_m kernel: [<c0142082>] kthread+0x42/0x70<BR>Oct 17
22:33:56 SANfile_m kernel: [<c0142040>] kthread+0x0/0x70<BR>Oct 17
22:33:56 SANfile_m kernel: [<c0105e6f>]
kernel_thread_helper+0x7/0x18<BR>Oct 17 22:33:56 SANfile_m kernel:
=======================<BR>Oct 17 22:33:56 SANfile_m kernel: error
1<BR></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=tore@linpro.no href="mailto:tore@linpro.no">Tore Anderson</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> Wednesday, October 17, 2007 6:01
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [dm-devel] multibus /
failover and EMC CX600</DIV>
<DIV><BR></DIV>* Gerald Nowitzky<BR><BR>> The mpath_prio_emc with
group_by_prio did the trick. Thanks!<BR>> <BR>> But I am still
loosing the paths to the failed devices. I Increased<BR>> dev_loss_tmo, but
the maximum seems to be about 600 - thus, after 10<BR>> Minutes, the paths
fail:<BR><BR>The maximum is indeed 600 seconds in 2.6.23.<BR><BR>>
SANfile_m linux # multipath -l<BR>> hcfshare
(360060160c820080063502869e459dc11) dm-0 ,<BR>> [size=3.4T][features=1
queue_if_no_path][hwhandler=1 emc]<BR>> \_ round-robin 0
[prio=0][enabled]<BR>> \_ #:#:#:# - #:#
[failed][undef]<BR>> \_ #:#:#:# - #:#
[failed][undef]<BR>> \_ round-robin 0 [prio=0][active]<BR>> \_
2:0:0:0 sdd 8:48 [active][undef]<BR>> \_ 1:0:0:0 sdb 8:16
[active][undef]<BR>> If I put them online again, I run into the -EEXIST
prob. Async SCSI<BR>> scanning *is* off in my kernel, so the only thing I
could do from<BR>> here is to try the patch, is it?<BR><BR>Matthew Wilcox'
patch solved this particular problem for me, yes. I<BR>still had some
problems with -EEXIST when unloading and re-inserting the<BR>HBA driver
module, though, but that's a corner case I rarely run into<BR>(as well as
being easily worked around by trying again).<BR><BR>Come to think of it, you
never said which kernel version you're running...?<BR><BR>> Oct 17 17:26:36
SANfile_m kernel: kobject_add failed for 1:0:1:0 with<BR>> -EEXIST, don't
try to register things with the same name in the same<BR>>
directory.<BR><BR>One suggestion... If the sysfs object is still around,
you might be<BR>able to delete it manually by running «echo 1
><BR>/sys/class/scsi_device/1:0:1:0/device/delete». If that works,
you can<BR>try to rescan again by doing «echo 0 1 0
><BR>/sys/class/scsi_host/host1/scan». With some luck it'll
work...<BR><BR>If it does, most of the time udev will notice and alert
multipath to<BR>check out the new device. Sometimes it doesn't work,
though - simply<BR>run the «multipath» command manually in that
case.<BR><BR>By the way - the «1» in «host1» maps to the first digit in
«1:0:1:0»,<BR>while the «0 1 0» in the echo command to the last
three.<BR><BR>Regards<BR>-- <BR>Tore Anderson<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>