Hi Jorge,
Thanks for your response!
> AFAIK autotrim is a pool property so not on a per-vdev basis.
I’m unable to find where vdev-specific vs zpool-wide properties are defined.
But the ‘zpool’ manage says this:
autotrim=on|off
When set to on space which has been recently freed, and is no
longer allocated by the pool, will be periodically trimmed. This
allows block device vdevs which support BLKDISCARD, such as SSDs,
or file vdevs on which the underlying file system supports hole-
punching, to reclaim unused blocks. The default setting for this
property is off.
Notice the "allows block device vdevs” and "such as SSDs, or file vdevs”
language, suggesting that it’s intended to be per-vdev…?
FWIW, the “ashift” description is also unclear, but Jim Salter’s article [1]
clearly states:
“The ashift property is per-vdev—not per pool,
as is commonly and mistakenly thought!"
[1]
https://arstechnica.com/information-technology/2020/05/zfs-101-understanding-zfs-storage-and-performance/
> I could be wrong though, I'm no zfs expert.
We’re always learning ;)
K.
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/T6ef0a71646a80e63-M6e8d685c9431770119381a21
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
