Date: Fri, 15 Apr 2016 10:48:07 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Warner Losh <imp@bsdimp.com>, Warren Block <wblock@wonkity.com> Cc: FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Samsung SSD TRIM [Was: Heads up] Message-ID: <57109CB7.3020204@FreeBSD.org> In-Reply-To: <CANCZdfqEWDLrHndKf8ZND1mM7spK9cq%2BnfnA79EVEaSj-MJfFA@mail.gmail.com> References: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> <alpine.BSF.2.20.1604142154240.8359@wonkity.com> <CANCZdfqEWDLrHndKf8ZND1mM7spK9cq%2BnfnA79EVEaSj-MJfFA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/04/2016 07:19, Warner Losh wrote: > Samsung 830 all firmware > Samsung 840 all firmware > Samsung 850 all firmware > > All of these are at least 18 months old (if not older). There's some > confusing in Linux lists on > the full impact of the Samsung drives (there was a bug in the Linux > implementation (that can't > be present in the FreeBSD implementation) that may have been the root cause > for the Samsung > black listing). Out of an abundance of caution, I've kept them in the list. For what it's worth, I have been using the following SSDs since September of 2015 : ada2: <Samsung SSD 850 EVO 120GB EMT01B6Q> ACS-2 ATA SATA 3.x device ada3: <Samsung SSD 850 EVO 120GB EMT01B6Q> ACS-2 ATA SATA 3.x device with ZFS with TRIM enabled and I haven't seen any problems thus far: $ sysctl kstat | fgrep trim kstat.zfs.misc.zio_trim.failed: 0 kstat.zfs.misc.zio_trim.unsupported: 2268 kstat.zfs.misc.zio_trim.success: 36895209 kstat.zfs.misc.zio_trim.bytes: 976003989504 Those disks are partitioned and host a small ZFS root / system pool plus log and cache vdevs for other HDD-based pool. So, I think that if the SSDs had any problem with TRIM I would have noticed it by now. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57109CB7.3020204>