Anyone else noticed issues with autotrim and zfs?

I turned on autotrim back when I created the pool

But based on the output of

zpool status -t

The trim status output only changes when I manually run the trim subcommand

Am i doing something wrong? or am i looking in the wrong place?

THanks,

@wendell

autotrim doesn’t show up in zpool status. It happens automatically in the background and isn’t displayed like resilver/scrub or manual trim.

According to OpenZFS documentation autotrim=on as well as periodic manual trim (I do this every week via cron) is recommended.

1 Like

then how can I/you know its doing it?
Or how often?
or how long it took… etc

for peace of mind… im thinking about turning autotrim off and then just using cron.monthly folder to schedule it.

1 Like

and while im complaining/whining…

why cant you trim l2arc devices?

https://openzfs.github.io/openzfs-docs/man/7/zpoolprops.7.html?highlight=autotrim

I’m not sure if there is more information available other than digging through the source code itself.

2 Likes

would you know if there an option for trimming the slog also?

While digging through my system and htop (with kernel threads visible, press capital K), I remembered your posting.

I checked for activity and I’ve seen very little activity/cpu cycles after my txg timeouts (bulk of data flushed to disk).

So there is something working which appears to look like the background trim of autotrim.

No f…clue :confused:

1 Like