TRIM erases user data

Steven Hartland steven at multiplay.co.uk
Thu Jun 18 00:31:05 UTC 2015


Just for the record illumos doesn't have any ZFS TRIM support.

> On 17 Jun 2015, at 17:25, Mark Saad <nonesuch at longcount.org> wrote:
> 
> 
> 
>> On Jun 17, 2015, at 7:55 PM, steven at multiplay.co.uk wrote:
>> 
>> We've used Samsung 840 Pro's on FreeBSD with ZFS for a long time (which has TRIM enabled by default) so as far unless this has been broken on a FW or HW version we've not used then I have no reason to believe we're effected by this issue at this time.
> 
> I was using 840 pros for zfs on freebsd 9.3 , 10.1 for 2 years with no issues . It was mostly for archival video storage and used as l2arc . 
> 
> I am working with  omnios and smartos (illumos / opensolaris) almost exclusively with zpools on ssds of various vendors and I haven't see this issue or similar issues . 
> 
> I am still using 4 840ev on a 10.1 zfs box for the pool , and one for a l2arc and it appears to be working as expected . 
> 
> For what my opinion is worth of this was some weird hardware bug , it wouldn't just effect Ubuntu. I think Ubuntu or better said the culture of Ubuntu might have a hand in this blog post .
> 
>> 
>> Sent from my iPad
>> 
>> On 17 Jun 2015, at 15:58, Mark Martinec <Mark.Martinec+freebsd at ijs.si> wrote:
>> 
>>>>> On 16 Jun 2015, at 18:51, grarpamp <grarpamp at gmail.com> wrote:
>>>>> https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
>>>>> https://github.com/torvalds/linux/blob/e64f638483a21105c7ce330d543fa1f1c35b5bc7/drivers/ata/libata-core.c#L4109-L4286
>>>>> http://www.aerospike.com/docs/operations/plan/ssd/ssd_certification.html
>>> 
>>> steven at multiplay.co.uk wrote:
>>>> This issue centers around queued TRIM requests at the ATA layer, which
>>>> is an extension that allows NCQ support for TRIM in the SATA 3.1 spec.
>>>> This is not something FreeBSD currently supports so is unaffected by
>>>> the issue at this time.
>>> 
>>> Are you sure? The article explicitly states they were not using
>>> queued TRIM:
>>> 
>>> | A lot of discussions started pointing out that the issue is related
>>> | to the newly introduced queued TRIM. This is not correct. The TRIM
>>> | on our drives is un-queued and the issue we have found is not related
>>> | to the latest changes in the Linux Kernel to disable this features.
>>> 
>>> 
>>> Mark
>>> _______________________________________________
>>> freebsd-fs at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
>>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>> _______________________________________________
>> freebsd-fs at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
> 
> 
> ---
> Mark Saad | nonesuch at longcount.org


More information about the freebsd-fs mailing list