Bug 1090476 - Stopping NetworkManager service leaves file systems on Linux Software RAID unmounted
Stopping NetworkManager service leaves file systems on Linux Software RAID un...
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
x86-64 Other
: P5 - None : Major (vote)
: ---
Assigned To: openSUSE GNOME
E-mail List
Depends on:
  Show dependency treegraph
Reported: 2018-04-22 16:51 UTC by Albert Hensel
Modified: 2018-06-16 13:18 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Albert Hensel 2018-04-22 16:51:57 UTC
Stopping NetworkManager with the command

$ systemctl stop NetworkManager

causes all file systems on MD RAID to be unmounted. The output from

$ journalctl -b -x

contains messages like

nm-dispatcher[4158]: ping: /dev/disk/by-id/md-uuid-775f49b4: Name or service not known


nm-dispatcher[4158]: ping: /dev/disk/by-id/md-uuid-d24b21d0: Temporary failure in name resolution

twice for every missing file system. Note that the full names of the links to the MD devices look like this:


If I remember correctly, the problem occurred the first time around April/Mai 2017.
Comment 1 Allan Greentree 2018-05-25 16:20:03 UTC
*** Bug 1090094 has been marked as a duplicate of this bug. ***
Comment 2 Albert Hensel 2018-06-16 13:18:49 UTC
Could this problem be caused by the colons in the device names? I replaced all entries


with the corresponding


in my /etc/fstab, and the file systems are no longer left unmounted when stopping NetworkManager.