------- Comment From thorsten.di...@de.ibm.com 2016-03-11 05:05 EDT------- (In reply to comment #27) > Here's my initial test with the merged multipath-tools test. > I had the FCP devices enabled with the 0.5.0+git<hash>-1ubuntu2 package > installed from the merges ppa and rebooted the system. > > After booting, I confirmed the paths were up, then used a vmcp command to > disconnect the devices. > I then queried mulitpath over a number of minutes to ensure the path remains > (but shows faulty). > After 15 minutues or so I contacted an admin to renable the FCP devices and > observed the paths > becoming restored in multipath
Ryan, congrats, well done. :-) I did an extended test with this multipathd/kpartx on a z/VM guest and in LPAR overnight and it ran very well. Even after 300 "off/on" cycles all paths were "active ready running" at the end. So, please go ahead with this. I will continue testing this when it is in xenial/main, since some of my other tests rely on this. I will close this defect when this fix is in xenial/main. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540407 Title: multipathd drops paths of a temporarily lost device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
