To: dorset@mailman.lug.org.uk
Subject: [Dorset] fstrim weirdness
Message-ID: <47abd098-4851-47a6-ca9e-adef6e5e5...@hamishmb.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi there,
I believe a while back I was talking about TRIM here, more specifically
about it not running aut
uk
Subject: [Dorset] fstrim weirdness
Message-ID: <47abd098-4851-47a6-ca9e-adef6e5e5...@hamishmb.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi there,
I believe a while back I was talking about TRIM here, more specifically
about it not running automatically on my systems, and
On 10/02/2022 11:07, Tim Waugh wrote:
On Thu, 10 Feb 2022 at 11:05, Hamish McIntyre-Bhatty
wrote:
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.
We only asked for
On Thu, 10 Feb 2022 at 11:05, Hamish McIntyre-Bhatty
wrote:
> 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.
>
We only asked for the fstrim timer. 'systemctl list-timers' will show you
On 10/02/2022 10:06, Tim Waugh wrote:
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty
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
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty
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,
On 09/02/2022 18:23, Neil Stone wrote:
See also 'anacron' to run cron tasks that were missed due to the system
being off.
Hi Victor, many years since we spoke last o/
On Wed, 9 Feb 2022 at 18:16, Victor Churchill
wrote:
I've not used fstrim, but I assume you're putting a fstrim command into
See also 'anacron' to run cron tasks that were missed due to the system
being off.
Hi Victor, many years since we spoke last o/
On Wed, 9 Feb 2022 at 18:16, Victor Churchill
wrote:
> I've not used fstrim, but I assume you're putting a fstrim command into
> your crontab but concerned that it
I've not used fstrim, but I assume you're putting a fstrim command into
your crontab but concerned that it won't run if the machine is shut down
before the cron time comes round.
Have you seen the cron '@reboot' facility? This will run whatever command
you give it when Linux starts.
You might want
I run this from root cron...
00 4 * * * /sbin/fstrim -av
you can, of course, change the timing to whatever you want.
HTH
On Wed, 9 Feb 2022 at 17:57, Hamish McIntyre-Bhatty
wrote:
> Hi there,
>
> I believe a while back I was talking about TRIM here, more
Hi there,
I believe a while back I was talking about TRIM here, more specifically
about it not running automatically on my systems, and I think someone
recommended I enable fstrim.service with systemd.
I finally got around to that, only to find that it was already enabled,
and apparently
11 matches
Mail list logo
