wickedd fails to start if local mount is nested over nfs mount
This document (7018322) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 12
For example /etc/fstab would look like this:
/dev/system/root / ext4 acl,user_xattr 1 1
nfs-server:/nfsmount /mnt-test nfs defaults 0 0 /dev/mapper/<dev-name> /mnt-test/data ext4 defaults 0 0
In this case, the local /dev/mapper/dev is mounted over the nfs mount: /nfsmount.
The following is logged in the boot messages:
systemd: Breaking ordering cycle by deleting job wickedd-nanny.service/start systemd: Job wickedd-nanny.service/start deleted to break ordering cycle starting with wicked.service/start systemd: Found ordering cycle on wicked.service/start systemd: Found dependency on wickedd.service/start systemd: Found dependency on local-fs.target/start systemd: Found dependency on mnt-test.mount/start systemd: Found dependency on mnt.mount/start systemd: Found dependency on network-online.target/start systemd: Found dependency on wicked.service/start systemd: Breaking ordering cycle by deleting job wickedd.service/start
/dev/mapper/<dev-name> /mnt-test/data ext4 defaults,_netdev 0 0
Now in this case the local fs (/dev/mapper) counts as filesystem based on network as well because it's mount point is on a network filesystem. However it's recognized as local fs and wickedd is tried to be started too early.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7018322
- Creation Date: 23-Nov-2016
- Modified Date:03-Mar-2020
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com