I have a CIFS mount of a single volume which then has 2 subdirectories bind mounted. Upon boot, systemd complains of an "ordering cycle" and fails to mount 1 of the binds but the other works fine. If I run mount -a
, the missing bind is mounted. I have been able to recreate this behavior in a new VM.
/etc/fstab
//server.example.com /mnt/media cifs [snip] 0 0
/mnt/media/secure /var/www/media/secure none bind 0 0
/mnt/media/public /var/www/media/public none bind 0 0
The bind mounts are not altered, those are the actual names. I don't know how, but, I think that may be significant, perhaps due to sort order because when I change the order in fstab
only the public
bind mount fails. secure
always works.
logs from journal
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Found dependency on var-www-media-public.mount/start
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Found dependency on mnt-media.mount/start
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Found dependency on network-online.target/start
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Found dependency on networking.service/start
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Found dependency on local-fs.target/start
Mar 19 14:06:45 ubuntu systemd[1]: local-fs.target: Breaking ordering cycle by deleting job var-www-media-public.mount/start
Mar 19 14:06:45 ubuntu systemd[1]: var-www-media-public.mount: Job var-www-media-public.mount/start deleted to break ordering cycle starting with local-fs.target/start
I've tried specifying x-systemd.requires=/mnt/media
on the bind mount but it made no change. I am at a loss for where to go next with this issue.