On Tue, Oct 15, 2024 at 3:59 AM Rusty Bird <rustyb...@net-c.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Boryeu Mao:
> > For the template install command on Qubes release 4.2.3
> >
> >    sudo qubes-dom0-update qubes-template-fedora-40-minimal
> >
> > I received a message that
> >
> >    fstrim: /var/tmp/tmpsd1ns61v/var/lib/qubes/vm-template: the discard
> > operation is not supported
>
> Did you maybe mount a tmpfs at /var/tmp? That would explain fstrim not
> working. It also wouldn't matter then.
>
>
It was the stock qubes-dom0-update, so all tmpfs operations are what the
stock script would do, no manual tmpfs mount.

> > The template appears to be running normally, so perhaps this is a
> warning
> > message.
>
> Pretty much. The fstrim invocation was added to inform the underlying
> storage (LVM Thin by default) of the filesystem hosting /var/tmp that
> the space previously used for temporary image files extracted during
> the installation process can be freed:
>
>
> https://github.com/QubesOS/qubes-core-admin-client/commit/4a9b57f91fdf3a2b35a5cf707970d05bf9cadba7
>
> But it doesn't affect the installed template.
>
>
In the qvm_template_postprocess.py (which the above link points to), fstrim
is called only if the root user does the template install.  So I'd need to
figure out:

(1) why is it that there is no need to free space in the lvm thin volume if
a non-root user does the install
(2) how would a root-installed template be different from one installed by
a non-root user

And if fstrim warning means the space didn't get freed as it should, then
perhaps I need to keep an eye on lvm volume usage.


> Rusty
>
>
Thank you very much for helping.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAOBBCnZAtdE%2BQVS%3DMhbuXCGEJGK2LAkCVZRRaOv1OFP1A%2Bjeng%40mail.gmail.com.

Reply via email to