[Bug 244692] gjournal: Does not support TRIM
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 16 Dec 2022 04:25:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244692
Alexey Dokuchaev <danfe@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danfe@FreeBSD.org
--- Comment #1 from Alexey Dokuchaev <danfe@FreeBSD.org> ---
I'm in the process of moving to an SSD, and now considering various approaches
to data storage. One of the things I wanted to try is UFS+gjournal(8)+async
which potentially performs noticeably better than ZFS, esp. on lower-end and
mobile CPUs, and gives explicit control over sync(2) and fsync(2) which e.g.
databases can benefit from.
Unfortunately, I've encountered the same problem as Paul: apparently
gjournal(8) does not propagate TRIM support from the drive to upper levels, so
even forcing TRIM on UFS won't help as underlying provider would just ignore
such requests rather than passing them down to the hardware.
(In reply to Paul from comment #0)
> It seems, gjournal still does not support TRIM in 2020?!.. neither for data
> device nor for journal device.
It's the end of 2022, and it still does not. ¯\_(ツ)_/¯
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.