Without the x-systemd.automount option just "mount /mnt/data" works fine
after reboot.
Regards,
Vlad.
On 31/07/17 16:36, Lennart Poettering wrote:
> On Do, 27.07.17 12:27, Vlad (vo...@vovan.nl) wrote:
>
>> Hello,
>>
>> Autogenerated from fstab mount unit fails, the relevant fstab entry:
>> UUID=xx /mnt/data btrfs
>> noatime,autodefrag,discard,subvol=data,nofail,noauto,x-systemd.automount
>>
>> 0 0
>>
>> >From log
>> Jul 27 12:09:15 xxx systemd[1]: mnt-data.automount: Got automount
>> request for /mnt/data, triggered by 2045 (ls)
>> Jul 27 12:09:15 xxx systemd[1]: Mounting /mnt/data...
>> Jul 27 12:09:15 xxx systemd[1]: mnt-data.mount: Mount process exited,
>> code=exited status=32
>> Jul 27 12:09:15 xxx systemd[1]: Failed to mount /mnt/data.
>> Jul 27 12:09:15 xxx systemd[1]: mnt-data.mount: Unit entered failed state.
>>
>>
>> Works fine with systemd versions < 234.
>
> Hmm, /bin/mount returns 32, which means "mount failure" according to
> its documentation...
>
> If you issue "mount UUID= /mnt/data
> btrfsnoatime,autodefrag,discard,subvol=data,nofail,noauto," on the
> shell, does it work then?
>
> Lennart
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
