Public bug reported:
The setup is - FC connected dual controller storage via single HBA on a Lenovo
Lenovo Flex System x240 M5 Compute Node
When a volume is unmapped by the storage the paths in multipath map are not
removed. dev_loss_tmo is set and the correct value is updated in the rport
sysfs. However paths stay:
360050763808081638000000000000056 dm-11 IBM,2145
size=6.0G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=0 status=enabled
|- 1:0:0:5 sdn 8:208 failed faulty running
`- 1:0:1:5 sdo 8:224 failed faulty running
Even when the map is flushed the paths are not removed by udev
The serious issue is that if another volume is mapped to the host with
the same LUN (the storage by default chooses the lowest unused LUN) the
paths are not updated by udev and are presented with wrong WWID (the old
one). This leads to serious data corruption as both volumes may be
presented as one multipath device.
In the man page multipath.conf(5)it says:
disable_changed_wwids
This option is deprecated and ignored. If the WWID of a
path suddenly changes, multipathd handles it as if it was removed and then
added again.
So this is not expected behaviour. The path are not checked at all if the WWID
has changed and the udev info shows the old device properties (not updated upon
path reinstated)
Flushing the map does not remove the path devices from the system also. They
are left orphaned and upon reload of the maps are readded, even if both path
are failing.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
apt-cache policy multipath-tools
multipath-tools:
Installed: 0.8.3-1ubuntu2
Candidate: 0.8.3-1ubuntu2
Version table:
*** 0.8.3-1ubuntu2 500
500 http://bg.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
sg3-utils:
Installed: 1.44-1ubuntu2
Candidate: 1.44-1ubuntu2
Version table:
*** 1.44-1ubuntu2 500
500 http://bg.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
sg3-utils-udev:
Installed: 1.44-1ubuntu2
Candidate: 1.44-1ubuntu2
Version table:
*** 1.44-1ubuntu2 500
500 http://bg.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://bg.archive.ubuntu.com/ubuntu focal/main i386 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
setting dev_loss_tmo to a certain value to be respected and paths to be removed
if failed
4) What happened instead
paths and map stay in "running" state and path are reused without wwid check
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: multipath-tools 0.8.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Jan 15 20:25:33 2021
InstallationDate: Installed on 2020-05-27 (233 days ago)
InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64
(20200203.1)
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: multipath-tools
UpgradeStatus: Upgraded to focal on 2021-01-14 (0 days ago)
mtime.conffile..etc.multipath.conf: 2021-01-15T19:42:30.753722
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
