Re: tunefs(8) changes don't stick

On Mon, Oct 18, 2021 at 5:11 PM Graham Perrin <grahamperrin@gmail.com>
wrote:

> On 18/10/2021 23:43, Kevin Oberman wrote:
>
> …
> > Isuspect that this problem is Bug 113912
> > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=113912>. While that
> > bug only references -L, I suspect that it applies to any tunefs(8)
> > modification to the root partition. …
>
>
> As far as I can tell,
>
> tunefs -j enable
>
> – does work as expected for
>
> /
>
> – but not with FreeBSD-provided disk images for FreeBSD 13.0-RELEASE and
> 13.0-STABLE
>
> <https://bugs.freebsd.org/bugzilla/show_btunefs -j enableug.cgi?id=259090
> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259090>>
>
> Tested so far: AMD64 .vhd files only. I assume that .qcow2, .raw and
> .vmdk files are similarly affected.
>

I have successfully updated the volume to TRIM by booting the install disk.
Everything I changed is working fine. I did an "fsck_ffs -E" to deal with
the 4 months I ran on the SSD without TRIM. Can't explain why "tunefs -j
enable" worked for you and not for me. Every tunable setting I tried
appeared to work when I did a 'tunefs -p', but went back to the prior state
when I mounted the disk RW (mount -u /). I'll admit that I have no idea how
being a VM might impact things, but it seems possible. My case is on bare
metal.

When trying to use tunefs on my boot disk, I never received any error or
warning. The changes just vanished. I might ask imp@ about this. He's
pretty expert on the boot process. I'll update the ticket as well.

Thanks, Graham, for the help that led me to look at the right place.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683