enable TRIM by default ?

Peter Jeremy peter at rulingia.com
Wed Dec 3 07:15:10 UTC 2014


On 2014-Dec-02 07:43:13 +0000, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
>Isn't it time that we enable TRIM by default in newfs ?

As an alternative viewpoint, I have a SSD that got severe indigestion when
I tried to enable TRIM:
aspire kernel: ad0: TIMEOUT - CFA ERASE retrying (1 retry left)
aspire kernel: ad0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
aspire kernel: ata1: error issuing SETFEATURES ENABLE WCACHE command
aspire kernel: ata1: error issuing SET_MULTI command
aspire kernel: ata1: error issuing WRITE_DMA command
The kernel then went to 1 core of interrupt and wedged.

I admit that it's about 3 years old but smartctl says it's still got lots of
life left in it and googling suggests they are still available.

The problem is that if a SSD doesn't support TRIM, it is likely to have all
sorts of misbehaviour if you attempt to enable TRIM.  If TRIM is enabled by
default, you need to provide a simple way to disable it if the system can't
cope.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20141203/031650e2/attachment.sig>


More information about the freebsd-arch mailing list