# Argument why (a) isn't a problem: the "paths are never going away"
And this is (as seen on the sysfs) on the rports, which are the links between local and remote FC ports. In my case for example two ports on each side doing NxM => 4 rports. -rw-r--r-- 1 root root 4096 Jan 21 15:51 /sys/class/fc_remote_ports/rport-0:0-0/dev_loss_tmo -rw-r--r-- 1 root root 4096 Jan 21 15:51 /sys/class/fc_remote_ports/rport-0:0-1/dev_loss_tmo -rw-r--r-- 1 root root 4096 Jan 21 15:51 /sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo -rw-r--r-- 1 root root 4096 Jan 21 15:51 /sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo Those rports do not go down at all when I unmap the disk, as the paths are unaffected. It more seems like kernel & multipath think "the paths are all happy and up, but something is wrong at the remote end" (which is true as we unmapped the disk). When the disk comes back everyone would expect and wan this to continue. E.g. in my case I "mapped back" the original volume and was happy that Mapping back the LUN: journal: Jan 25 08:16:46 s1lp5 kernel: sd 0:0:1:1074413604: Power-on or device reset occurred Jan 25 08:16:46 s1lp5 kernel: sd 1:0:1:1074413604: Power-on or device reset occurred Jan 25 08:16:46 s1lp5 kernel: sd 1:0:0:1074413604: Power-on or device reset occurred Jan 25 08:16:46 s1lp5 kernel: sd 0:0:1:1074413604: alua: port group 00 state A preferred supports tolusnA Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: sdh - tur checker reports path is up Jan 25 08:16:47 s1lp5 multipathd[782]: 8:112: reinstated Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: remaining active paths: 1 Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: sdr - tur checker reports path is up Jan 25 08:16:47 s1lp5 multipathd[782]: 65:16: reinstated Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: remaining active paths: 2 Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: sdm - tur checker reports path is up Jan 25 08:16:47 s1lp5 multipathd[782]: 8:192: reinstated Jan 25 08:16:47 s1lp5 multipathd[782]: mpathb: remaining active paths: 3 Jan 25 08:16:47 s1lp5 kernel: device-mapper: multipath: Reinstating path 8:112. Jan 25 08:16:47 s1lp5 kernel: device-mapper: multipath: Reinstating path 65:16. Jan 25 08:16:47 s1lp5 kernel: device-mapper: multipath: Reinstating path 8:192. Jan 25 08:16:47 s1lp5 systemd-udevd[648]: Worker [18540] terminated by signal 9 (KILL) Jan 25 08:16:47 s1lp5 systemd-udevd[648]: dm-3: Worker [18540] failed Jan 25 08:16:47 s1lp5 kernel: sd 0:0:1:1074413604: alua: port group 00 state A preferred supports tolusnA Jan 25 08:16:47 s1lp5 kernel: sd 0:0:1:1074413604: alua: port group 00 state A preferred supports tolusnA Jan 25 08:16:48 s1lp5 dbus-daemon[1048]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=0 pid=983318 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined") Jan 25 08:16:48 s1lp5 systemd[1]: Starting PackageKit Daemon... Jan 25 08:16:48 s1lp5 PackageKit[983321]: daemon start Jan 25 08:16:48 s1lp5 kernel: sd 0:0:0:1074413604: Power-on or device reset occurred Jan 25 08:16:48 s1lp5 kernel: sd 0:0:0:1074413604: alua: port group 00 state A preferred supports tolusnA Jan 25 08:16:49 s1lp5 dbus-daemon[1048]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 25 08:16:49 s1lp5 systemd[1]: Started PackageKit Daemon. Jan 25 08:16:49 s1lp5 multipathd[782]: mpathb: sdc - tur checker reports path is up Jan 25 08:16:49 s1lp5 multipathd[782]: 8:32: reinstated Jan 25 08:16:49 s1lp5 multipathd[782]: mpathb: remaining active paths: 4 Jan 25 08:16:49 s1lp5 kernel: device-mapper: multipath: Reinstating path 8:32. Jan 25 08:16:49 s1lp5 kernel: sd 0:0:0:1074413604: alua: port group 00 state A preferred supports tolusnA Jan 25 08:16:49 s1lp5 kernel: sd 0:0:0:1074413604: alua: port group 00 state A preferred supports tolusnA New multipath state: mpathb (36005076306ffd6b6000000000000240a) dm-3 IBM,2107900 size=10G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw `-+- policy='service-time 0' prio=50 status=active |- 0:0:0:1074413604 sdc 8:32 active ready running |- 0:0:1:1074413604 sdh 8:112 active ready running |- 1:0:1:1074413604 sdr 65:16 active ready running `- 1:0:0:1074413604 sdm 8:192 active ready running So it detected that it is back and re-established things just as I would expect. It was never fully "dead" as the paths were just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911999 Title: faulty paths are not removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1911999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
