jessie: help debugging NFS shares not mounted at boot, double mounts with mount -a, and @reboot cronjobs

[Felipe Sateler]

On 19 February 2016 at 09:11, Sandro Tosi <morph at debian.org> wrote:
> Hey Felipe,
>
> On Thu, Feb 18, 2016 at 5:39 PM, Felipe Sateler <fsateler at debian.org> wrote:
>> That mail has:
>> 1711:Feb 10 16:44:40 SERVER systemd[1]: mnt-NFSSERVER.mount changed
>> dead -> mounting
>> 1817:Feb 10 16:44:43 SERVER systemd[1]: mnt-NFSSERVER.mount changed
>> mounting -> mounted
>> 1818:Feb 10 16:44:43 SERVER systemd[1]: Job mnt-NFSSERVER.mount/start
>> finished, result=done
>> 1819:Feb 10 16:44:43 SERVER systemd[1]: Mounted /mnt/NFSSERVER.
>> 2106:Feb 10 16:44:43 SERVER systemd[1]: mnt-NFSSERVER.mount changed
>> mounted -> dead
>> 2107:Feb 10 16:44:43 SERVER systemd[1]: Failed to destroy cgroup
>> /system.slice/mnt-NFSSERVER.mount: Device or resource busy
>> 2632:Feb 10 16:44:54 SERVER systemd[1]: mnt-NFSSERVER.mount changed
>> dead -> mounted
>>
>> So somehow the mount finishes successfully but the mount is declared
>> dead in rapid succession. This would suggest that systemd regards
>> remote-fs up at the time of the mount success exit, but the mount then
>> dies and revives some seconds later.
>
> thanks for reading this to me! I somehow missed the mounted-dead-mounted
> again dance.
>
>> Are there any possibly relevant logs during that time?
>
> I extended a bit the grep on the logs:
>
> 1005:Feb 10 16:44:38 SERVER systemd[1]: Installed new job
> mnt-NFSSERVER.mount/start as 97
> 1707:Feb 10 16:44:40 SERVER systemd[1]: Mounting /mnt/NFSSERVER...
> 1709:Feb 10 16:44:40 SERVER systemd[1]: About to execute: /bin/mount -n
> XXX.YYY.16.226:/VOL /mnt/NFSSERVER -t nfs -o
> rw,intr,tcp,bg,rdirplus,noatime,_netdev
> 1710:Feb 10 16:44:40 SERVER systemd[1]: Forked /bin/mount as 583
> 1711:Feb 10 16:44:40 SERVER systemd[1]: mnt-NFSSERVER.mount changed dead ->
> mounting
> 1713:Feb 10 16:44:40 SERVER systemd[583]: Executing: /bin/mount -n
> XXX.YYY.16.226:/VOL /mnt/NFSSERVER -t nfs -o
> rw,intr,tcp,bg,rdirplus,noatime,_netdev

I now noticed this flag (bg). What happens if you remove it? This flag
sounds like it could confuse systemd as to when the mounts are
actually ready.

-- 

Saludos,
Felipe Sateler