On Sun, 2017-04-02 at 04:09 +0200, Alban Browaeys wrote: > I guess the issue is a mix of this old behaviour : > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html- > single/DM_Multipath/ > In older releases of Red Hat Enterprise Linux, multipath always tried > to create a multipath device for every path that was not explicitly > blacklisted. In Red Hat Enterprise Linux 6, however, if the > find_multipaths configuration parameter is set to yes, then multipath > will create a device only if one of three conditions are met > (...) > > [ Note that find_multipaths is set to no here.] > > and the 60-multipath.rules in March 2017 which ends up tagging all the > partitions with SYSTEMD_RUN=O. > Which is fine if all of them are dm ones (as they are later tagged > back to SYSTEMD_RUN=1 , but not so fine for "bare metal partitions" > that are left so. > > To reproduce I add my disk wwid (here <n> is the disk serial) to > /etc/multipath/wwids > /WDC_WD10SPCX-08S8TT0_WD-<n>/ > and with sda7 a "bare metal" partition on this disk (here /boot): > sudo sh -c "env - SEQNUM="1" ACTION="add" $(udevadm info -x /dev/sda7|sed -n > '/^E:/ { s@E: \(.*\)=\(.*\)@\1="\2"@p }' | tr '\n' ' ' ) /sbin/multipath > -u /dev/sda7; ";echo $? > I get: > /dev/sda7 is a valid multipath device path > 0 > thus this "non multipath, non dm" partition will be tagged not ready to > systemd. > (this also mean this requires a non dm partition). > > If /etc/mulitpath/wwids is missing or left empty, obviously the bug is not > reproducible. > I need guidance as to what creates or was creating this file at one point in > time.
It is (lib)multiapth that creates the file. This feature seems to be new code, introduced in the last year, something that I am not very familiar with. But I am still wondering how that file got created, because we don't seem to ship it. From what I skimmed so far, you must be invoking its trigger through multipath cli. What all options are you using ? Otherwise, it should be triggered by the find_mulitpaths=yes feature. > I tried removing it, then flusing, no luck so far. > Otherwise I would say let s close this bug :) > > > Thanks > Alban > > PS: multipath was never setup on this box. The package was installed only > (this is a laptop). > This install dates back to at least 0.5.0+git1.656f8865-8 (from apt history). Which is what confuses me. If it was never setup, I'm not sure what would trigger the creation of the wwids_file. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
