Autotrim is set per zpool, not per vdev. You can also manually trim individual disk using ‘zpool trim pool disk’
From: Kent Watsen <k...@watsen.net> Date: Wednesday, April 28, 2021 at 9:11 AM To: illumos-discuss <discuss@lists.illumos.org> Cc: illumos-zfs <z...@lists.illumos.org> Subject: [zfs] Re: [discuss] zpool add -o autotrim=on doesn't work? [CC-ing Illumos-zfs, as I just got added. For those new to this thread, please see this permalink: https://illumos.topicbox.com/groups/discuss/T6ef0a71646a80e63-Mff037ef74dc10571c74cdd7e] Thank you all that have responded thus far! I’m surprised my top-line question isn't answered yet, given that having an SSD-based ZIL/SLOG for a spinning rust based pool must be very common and well known…like, from a decade ago ;) Here's the questions again: 1) assuming "autotrim=on" should be set for the SSD-based “log” vdev, and yet makes no sense for HDD (spinning rust) based pool, is it expected to set the “autotrim” property for the whole-pool (assuming it’s ignored by the the HDDs that don’t support TRIM) or for just the “log” vdev? 2) assuming it’s best to set "autotrim=on” for just the “log” vdev, why is the command shown in the permalink above failing? Thanks, Kent ------------------------------------------ illumos: illumos-zfs Permalink: https://illumos.topicbox.com/groups/zfs/T6ef0a71646a80e63-Mad79a9db736819f810c3facd Delivery options: https://illumos.topicbox.com/groups/zfs/subscription ------------------------------------------ illumos: illumos-discuss Permalink: https://illumos.topicbox.com/groups/discuss/T6ef0a71646a80e63-Mb98cbb03644b5f4fb6195f17 Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
