So, from a systemd POV everything looks correct: Names=nfs.mount Requires=-.mount system.slice Wants=network-online.target Conflicts=umount.target Before=umount.target nfs-p2_home.mount remote-fs.target After=-.mount network-online.target remote-fs-pre.target network.target system.slice
Names=nfs-p2_home.mount Requires=-.mount system.slice Wants=network-online.target Conflicts=umount.target Before=umount.target remote-fs.target After=remote-fs-pre.target network-online.target system.slice network.target nfs.mount -.mount RequiresMountsFor=/nfs The generated orderings (like After=network.target) are correct and should ensure that on shutdown the mounts are stopped before network.target is stopped. This requires though, that the network configuration (and all the tools related to it) properly hook into network.target and order themselves accordingly. E.g. wpasupplicant.service was for a long time buggy, in that it didn't orther itself Before=network.target. The result was, that on shutdown wpasupplicant was stopped to early. So this looks like either an issue in ifupdown or ovs, or the interaction between the two. A verbose shutdown log should give us a better clue and also a systemd-analyze output regarding the orderings. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
