* Matt Taggart [230419 04:22]:
> On 4/15/23 15:35, Chris Hofstaedtler wrote:
>
> > > This behavior might follow the principle of least surprise, but I think
> > > for
> > > SSD based systems it is losing out on the benefits of TRIM/discard
> > > (improved
> > > i/o latency, flash wear).
> >
>
On 4/15/23 15:35, Chris Hofstaedtler wrote:
This behavior might follow the principle of least surprise, but I think for
SSD based systems it is losing out on the benefits of TRIM/discard (improved
i/o latency, flash wear).
Yes. Also it is - to the best of my knowledge - the only way of not
* Matt Taggart [230414 19:54]:
> I recently noticed on my existing bullseye systems that fstrim.timer is not
> enabled by default:
[..]
> It looks this way on all my bullseye systems that were older and
> dist-upgraded to bullseye. I only have one system that was installed
> directly with
Package: util-linux
Version: 2.36.1-8+deb11u1
I recently noticed on my existing bullseye systems that fstrim.timer is
not enabled by default:
===
# systemctl status fstrim.timer
● fstrim.timer - Discard unused blocks once a
4 matches
Mail list logo
