Description of problem: I've got this mapping: # multipath -ll mpath0 () dm-0 NETAPP,LUN [size=1.0T][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=100][active] \_ 3:0:1:0 sdb 8:16 [active][ready] \_ 4:0:0:0 sdd 8:48 [active][ready] \_ round-robin 0 [prio=20][enabled] \_ 3:0:0:0 sdc 8:32 [active][ready] \_ 4:0:1:0 sde 8:64 [active][ready] Pull the cable to controller 4 and about 15 seconds later the kernel starts removing those disks. The map now looks like this: mpath0 () dm-0 NETAPP,LUN [size=1.0T][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=50][active] \_ 3:0:0:0 sdb 8:16 [active][ready] \_ #:#:#:# - #:# [active][faulty] \_ round-robin 0 [prio=10][enabled] \_ 3:0:1:0 sdc 8:32 [active][ready] \_ #:#:#:# - #:# [active][faulty] Plug the cable back in and the kernel complains and Call Traces (see attach for full dmesg): sysfs: duplicate filename '4:0:0:0' can not be created ... kobject_add_internal failed for 4:0:0:0 with -EEXIST, don't try to register things with the same name in the same directory. The disks seem to come back as /dev/sdf and /dev/sdg, but multipath doesn't notice and the kernel isn't happy either. I don't really know how to get the map back to normal without rebooting. :( Version-Release number of selected component (if applicable): device-mapper-multipath-0.4.7-16.fc9.x86_64 kernel-2.6.25.14-108.fc9.x86_64 udev-124-2.fc9.x86_64 How reproducible: always Expected results: the paths to come back to active
Created attachment 314366 [details] dmesg
From what I read, it looks like the way you are going to handle this is through the udev socket: multipath_event? I recompiled the current version in rawhide (0.4.8-6) for F9: 1. the config_space_fix.patch was unable to parse my config (noted this in bug #457530). reverted it locally. 2. added RUN+="socket:/org/kernel/dm/multipath_event" to my local udev ruleset file. I didn't touch anything in 40-multipath.rules, I imagine maybe these rules clash with the socket, but... after the above, multipathd seems to notice the disappearance and reappearance of my disk fine. No kernel call traces either.
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.