Date: Mon, 28 Aug 2023 21:09:55 +0100 From: Bob Bishop <rb@gid.co.uk> To: Alexander Motin <mav@FreeBSD.org> Cc: Pete Wright <pete@nomadlogic.org>, "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org> Subject: Re: zfs autotrim default to off now Message-ID: <F934C7A5-9848-4DB2-A80F-7537F6804363@gid.co.uk> In-Reply-To: <21ef6e61-8985-9c62-b400-fe4200063e35@FreeBSD.org> References: <cpzqsgncysqm4xwarzue2n6vxpzw2yl4owlcwf64mcgzleclbb@eltdofcwp6iw> <de2b9081-4f3b-c19b-b658-08dd9acb563d@FreeBSD.org> <ffa25b60-3500-6006-0a35-2b9ffd3b2c2c@nomadlogic.org> <21ef6e61-8985-9c62-b400-fe4200063e35@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > On 28 Aug 2023, at 20:00, Alexander Motin <mav@FreeBSD.org> wrote: >=20 > On 28.08.2023 13:56, Pete Wright wrote: >> So to be clear, if we were using the default autotrim=3Denabled = behavior we in fact weren't having our SSDs trimmed? I think that's my = concern, as an admin I was under the impression that it was enabled by = default but apparently that wasn't actually happening. >=20 > We wanted autotrim to be enabled by default, but it was not enabled, = and it was reported as not enabled, so there should be no confusion. = The only confusion may have been if you tried to read the code and see = it should have been enabled. >=20 > --=20 > Alexander Motin Prompted by this thread, I went to check one of my servers that predates = the change to OpenZFS. I set autotrim=3Don at the time of the = transition; at some point since, it had become unset (and not by me). = The system has been upgraded from time to time and is currently running = 13.2R.=20 -- Bob Bishop rb@gid.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F934C7A5-9848-4DB2-A80F-7537F6804363>