Re: [arch-general] Samsung EVO 850 TRIM Bug Fixed?

[Andrew Martin]

Thanks for the clarification on this!

Andrew

On 14 January 2016 at 19:43, Gustavo De Nardin (spuk) 
wrote:

> On 14 January 2016 at 21:10, Mauro Santos 
> wrote:
>
> > There were two different bugs that came up at different times, one is
> > drives that don't work properly with queued trim and another was the bug
> > with raid.
> >
>
> Alright, thanks for clearing that up. I see there's still a big list of
> drives needing workarounds. (
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/ata/libata-core.c#n4097
> )
>
>
>
> > The fix for the first problem is still to blacklist queued trim for the
> > affected drives, it hasn't changed. Both problems should not affect
> > either the "normal" or lts kernels provided by arch.
> >
>
>
> --
> (nil)
>

[arch-general] Samsung EVO 850 TRIM Bug Fixed?

[Andrew Martin]

Hello,

I installed Arch on an EVO 850 120GB SSD. I read about the linux EVO
800-series
TRIM bug a few months ago:
https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/

However it appeared to have been fixed in the 4.1 kernel release:
https://github.com/torvalds/linux/commit/9a9324d3969678d44b330e1230ad2c8ae67acf81

However a few days ago, my root partition suddenly became corrupted and I
was
forced to reinstall. While I cannot be 100% certain it was this bug, it
seems
likely. Has it been confirmed that this bug has been fixed in Arch? If so,
at
which kernel version?

Thanks,

Andrew