07.03.2016 21:41, Greg Freemyer пишет:
The destination does not exist (it used to).
But ignoring that rather big issue, why does a failed mount of a tertiary filesystem cause systemd to crash and burn.
Because all mount points in /etc/fstab are mandatory unless marked as optional. There is nothing new - countless number of times I had to "fix" server that stayed in "rescue mode" because someone removed access to SAN storage but forgot to edit fstab. Without any systemd involved.
If no one knows, I'll just open this as a bugzilla.
BTW; This isn't a --bind mount. It is a loopback mount. I'm supposed to have a large file at /srv_new/portal_backup_container that itself is a filesystem that I loopback mount.
I know that is strange, but it is needed to overcome an issue with the NFS mount options setup my my cloud provider. Inside the loopback mount I have total control of the mount options.
Greg
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org