noauto option ignored in /etc/fstab?

[Tom H]

On Tue, Dec 5, 2017 at 5:52 AM, Josef Wolf <jw at raven.inka.de> wrote:
> On Mon, Dec 04, 2017 at 05:18:56PM -0500, Tom H wrote:


>> "/etc/init.d/grub-common" has a "case" statement with
>>
>> start|restart|force-reload)
>> log_action_msg "Recording successful boot for GRUB"
>> [ -s /boot/grub/grubenv ] || rm -f /boot/grub/grubenv
>> mkdir -p /boot/grub
>> grub-editenv /boot/grub/grubenv unset recordfail
>> log_end_msg $?
>>
>> so "/boot" is being mounted in spite of the "noauto" :(
>>
>> root at jwolf:~# systemctl status boot.mount
>
> Seems that we're getting closer here:
>
>    # systemctl status boot.mount
>    ● boot.mount - /boot
>       Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
>       Active: inactive (dead)
>        Where: /boot
>         What: /dev/disk/by-uuid/2b61601c-84d6-47a5-80eb-9149ce116be8
>         Docs: man:fstab(5)
>               man:systemd-fstab-generator(8)
>
>    Dez 04 10:56:52 bu201 systemd[1]: Mounting /boot...
>    Dez 04 10:56:52 bu201 systemd[1]: Mounted /boot.
>
> Note the time stamp: that was the time the system was booted.
>
> I understand that grub wants to remember that the last boot was successful.
>
> But:
> 1. It stores only an empty /boot/grub/grubenv (1024 bytes of '#' characters)
> 2. shouldn't it undo what it have done? When it needs to mount an unmounted
>    partition, it should umount this partition again when done.

I disable grub-common on my Ubuntu and Debian systems, so I don't
really care what/where/how.

I suspect that the great majority of Ubuntu installations "/boot" is
always mounted, even if it's a separate filesystem but you could file
an RFE to take your use-case into account.


>> [You might want to add "x-systemd.auto" to the "/boot" line in
>> ?etc/fstab". "/boot" will be automounted when it's needed.]
>
> Will this umount the partition again when it's no longer needed?

You can add "x-systemd.idle-timeout=xxx" too.