Description of problem: With NFS mounts in an fstab it appears that NetworkManager and the autogenerated mount units get into a dependency loop which causes a number of important units to get discarded while trying to resolve the issue. Version-Release number of selected component (if applicable): Seen in FC16,17,18 How reproducible: Every boot with NFS mounts in the fstab Steps to Reproduce: 1. Try and boot a system with NFS mounts in the fstab. 2. 3. Actual results: Several units are deleted and never attempt to stop, several others fail because the root filesystem doesn't get remounted RW until other units time out. Expected results: System should come up, remount the root filesystem RW, mount NFS volumes in the fstab without dependency loops or units timing out. Additional info:
[ 6.943559] systemd[1]: Found ordering cycle on NetworkManager-wait-online.service/start [ 6.943707] systemd[1]: Walked on cycle path to NetworkManager.service/start [ 6.943810] systemd[1]: Walked on cycle path to dbus.socket/start [ 6.943912] systemd[1]: Walked on cycle path to sysinit.target/start [ 6.944039] systemd[1]: Walked on cycle path to local-fs.target/start [ 6.944141] systemd[1]: Walked on cycle path to var-storage-fuse-mp3.mount/start [ 6.944287] systemd[1]: Walked on cycle path to var-storage.mount/start [ 6.944388] systemd[1]: Walked on cycle path to remote-fs-pre.target/start [ 6.944490] systemd[1]: Walked on cycle path to network.target/start [ 6.944588] systemd[1]: Walked on cycle path to NetworkManager-wait-online.service/start [ 6.944735] systemd[1]: Breaking ordering cycle by deleting job NetworkManager.service/start [ 6.944883] systemd[1]: Job NetworkManager.service/start deleted to break ordering cycle starting with NetworkManager-wait-online.service/start [ 6.945103] systemd[1]: Deleting job NetworkManager-wait-online.service/start as dependency of job NetworkManager.service/verify-active
Same problem here during reboot on Fedora 19: Aug 4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to nfs-darwin.mount/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to network.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to NetworkManager.service/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to dbus.socket/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to sysinit.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Breaking ordering cycle by deleting job nfs-darwin.mount/stop Aug 4 16:18:43 edison systemd[1]: Job nfs-darwin.mount/stop deleted to break ordering cycle starting with local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Found ordering cycle on local-fs.target/stop Aug 4 16:18:43 edison systemd[1]: Walked on cycle path to nfs-darwin-home.mount/stop /etc/fstab contains: darwin:/ /nfs/darwin nfs4 rw,soft,intr,noauto 0 0
This should be fixed by the latest f18 systemd update.