[systemd-devel] systemd 219 unmounting things unexpectedly
Canek Peláez Valdés
caneko at gmail.com
Sun Mar 29 17:56:08 PDT 2015
On Sun, Mar 29, 2015 at 6:48 PM, Steven Noonan <steven at uplinklabs.net>
wrote:
>
> 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?
https://bugs.freedesktop.org/show_bug.cgi?id=89383
The propose patch works for me.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150329/d4c55090/attachment.html>
More information about the systemd-devel
mailing list