On Wed, Jun 17, 2015 at 12:24:55PM +1000, Adam Carter wrote:
> /* devices that don't properly handle queued TRIM commands */
> Micron_M500*
> Crucial_CT*M500*
> Micron_M5[15]0*
> Crucial_CT*M550*
> Crucial_CT*MX100*
> Samsung SSD 8*
>
> from drivers/ata/libata-core.c
Then read further:
* Whitelist drives that are known to reliably return zeroes
* after TRIM.
* The intel 510 drive has buggy DRAT/RZAT. Explicitly exclude
* that model before whitelisting all other intel SSDs.
*/
{ "INTEL*SSDSC2MH*", NULL, 0, },
{ "Micron*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "Crucial*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "INTEL*SSD*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "SSD*INTEL*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "Samsung*SSD*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "SAMSUNG*SSD*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
{ "ST[1248][0248]0[FH]*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, }
> More info:
> http://linux.slashdot.org/story/15/06/16/201217/trim-and-linux-tread-cautiously-and-keep-backups-handy
>
> Also, my samsung 840 is slow (multisect is off and cant be enabled with
> hdparm). Tried update the bios but the boot cd crashed on my machine (AMD
> chipset related) so i will have to put it in another machine and try
> again...
>
> Samsung EVOs also have a firmware bug that causes them to slow down.
I chose long ago not to use queued TRIM (when OCZs were the rage).
>From a cursory read this sounds like *only* ext4 fs. I have XFS on all my
SSDs. Two are Samsung 840 Pro Series, and 850 Pro Series. The 840 I've had
over a year and it is golden. The 850 I've had only a couple of months, and
due to work requirements it is running Windows atm. Still, there is nothing
like what I read in this article happening with either.
I also have a Micron C400 RealSSD mSATA 32GB -- no problems with it, either.
It's running Funtoo atm with VFAT /boot for UEFI, swap, all other XFS.
