On 10/02/2022 10:06, Tim Waugh wrote:
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty <d...@hamishmb.com>
wrote:
I finally got around to that, only to find that it was already enabled,
and apparently not doing anything. As I don't leave my systems on 24/7,
is it safe to assume that the timer isn't firing when the system is
booted up later, after the configured time for TRIM has passed?
This depends on the configuration of the timer. The 'Persistent' field
controls this (see systemd.timer(5) ).
What does this say?:
systemctl show fstrim.timer | grep Persistent
Also, find out when it last triggered:
systemctl list-timers fstrim
Tim.
*/
Hello Tim.
Persistent=yes is what I get from that command.
The second command says it was "Passed" three days ago, but I don't know
if that means it ran. There are no other timers in the output from that
command.
Perhaps TRIM has been working fine, given my heavy-IO workload, but when
I do run it manually it often has done 100s of GB at a time in the past.
Hamish
--
Next meeting: Online, Jitsi, Tuesday, 2022-03-01 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
