Date: Fri, 15 Apr 2016 12:20:15 +0100 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-current@freebsd.org Subject: Re: Samsung SSD TRIM [Was: Heads up] Message-ID: <5710CE6F.6010408@multiplay.co.uk> In-Reply-To: <20160415081130.GH2282@home.opsec.eu> References: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> <alpine.BSF.2.20.1604142154240.8359@wonkity.com> <CANCZdfqEWDLrHndKf8ZND1mM7spK9cq%2BnfnA79EVEaSj-MJfFA@mail.gmail.com> <57109CB7.3020204@FreeBSD.org> <20160415081130.GH2282@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/04/2016 09:11, Kurt Jaeger wrote: > Hi! > > avg wrote: >> 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 > I have one in use with zfs and trim: > > ada1: <Samsung SSD 840 EVO 250GB EXT0BB6Q> ACS-2 ATA SATA 3.x device > > Works as my ports build hosts, and is fine as far as I can see. > Prior to Warners commit there was no NCQ TRIM support in FreeBSD, so while it was working with standard non-NCQ TRIM (and I can corroborate that as we use the 840's and 850's all over with ZFS with TRIM enabled) its possible that it could cause issues when NCQ TRIM comes into play. From what I read when this issue first came to light, I believe the actual issue was a Linux kernel bug not a FW bug in Samsung drives that caused the corruption. This is the thread which details said issue: http://www.spinics.net/lists/raid/msg49440.html Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5710CE6F.6010408>