[systemd-devel] systemd 219 unmounting things unexpectedly

[Steven Noonan]

This is weird. I issued a 'mount' command, which succeeds, but then
systemd jumps in and immediately unmounts it. What's going on here?

Command issued:

mount -o loop,ro someisofile.iso /mnt

Journal shows this mess:

Mar 29 17:39:06 loki systemd[2460]: Unit mnt.mount is bound to
inactive unit. Stopping, too.
Mar 29 17:39:06 loki systemd[1]: Unit mnt.mount is bound to inactive
unit. Stopping, too.
Mar 29 17:39:06 loki systemd[2480]: Unit mnt.mount is bound to
inactive unit. Stopping, too.
Mar 29 17:39:06 loki systemd[2460]: Unmounting /mnt...
Mar 29 17:39:06 loki systemd[2480]: Unmounting /mnt...
Mar 29 17:39:06 loki systemd[1]: Unmounting /mnt...
Mar 29 17:39:06 loki systemd[1]: mnt.mount mount process exited,
code=exited status=32
Mar 29 17:39:06 loki systemd[1]: Unmounted /mnt.
Mar 29 17:39:06 loki systemd[1]: Unit mnt.mount entered failed state.
Mar 29 17:39:06 loki systemd[2460]: mnt.mount mount process exited,
code=exited status=1
Mar 29 17:39:06 loki systemd[2460]: Unmounted /mnt.
Mar 29 17:39:06 loki systemd[2460]: Unit mnt.mount entered failed state.
Mar 29 17:39:06 loki umount[4173]: umount: /mnt: not mounted
Mar 29 17:39:06 loki umount[4175]: umount: /mnt: not mounted
Mar 29 17:39:06 loki systemd[1]: mnt.mount failed to run 'mount' task:
No such file or directory
Mar 29 17:39:06 loki systemd[1]: Failed to mount /mnt.
Mar 29 17:39:06 loki systemd[1]: Mounting /mnt...
Mar 29 17:39:06 loki systemd[2480]: Unmounted /mnt.

systemd[1] is obviously PID1.
systemd[2460] is the 'systemd --user' for my user
systemd[2480] is the 'systemd --user' for root

Why all three observed the '/mnt' mount appearing and all three
decided to issue the unmount is beyond me.

What inactive unit is it talking about? I don't have a 'mnt.mount'
unit anywhere. Why did systemd decide to do this? Is there a way to
tell systemd to keep its hands off?