Date: Fri, 08 Dec 2023 15:55:08 +0100 From: Olivier Certner <olivier.freebsd@free.fr> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: periodic trim for ufs2 ssds Message-ID: <85152060.0ko45tJjV3@ravel> In-Reply-To: <CANCZdfro4MpuCqi1xwi3RJUqUg7g4H%2BBGabN0MCjq7nD%2BZf-9g@mail.gmail.com> References: <ZXHTAIPnrEOq4iaV@int21h> <2959153.slGk94SIus@ravel> <CANCZdfro4MpuCqi1xwi3RJUqUg7g4H%2BBGabN0MCjq7nD%2BZf-9g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I wouldn't expect that to work... Indeed, it can't possibly work if fsck cannot know the inflight block allocations, which I don't think it can know. So I'd say instead that, if 'fsck_ffs -B -E' doesn't spit out an error, then it's probably a bug... > I'd go the other way. I'd turn trim on for UFS and monitor the system under > load. Newer drives I've evaluated have much better pathological behavior > than the drives of a few years ago... there's a lot of left over fud about > how it's always terrible... Personally, I've never bothered and have always turned trimming on on UFS, without practical problems. Regards. -- Olivier Certner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85152060.0ko45tJjV3>