From: Christian <cdysthe@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: trim not working and irreparable errors from btrfsck
Date: Wed, 17 Jun 2015 11:40:33 -0400 [thread overview]
Message-ID: <mls4dj$2oh$1@ger.gmane.org> (raw)
In-Reply-To: <CAJCQCtTJU3z4je=CBWDP6qE7_rDt46ivYBs9T1NNj3b-5Fy_PA@mail.gmail.com>
On 06/17/2015 11:28 AM, Chris Murphy wrote:
>>
>> However, fstrim still gives me "0 B (0 bytes) trimmed, so that may be
>> another problem. Is there a way to check if trim works?
>
> That sounds like maybe your SSD is blacklisted for trim, is all I can
> think of. So trim shouldn't be the cause of the problem if it's being
> blacklisted. The recent problems appear to be around newer SSDs that
> support queue trim and newer kernels that issue queued trim. There
> have been some patches related to trim to the kernel, but the
> existence of blacklisting and claims of bugs in firmware make it
> difficult to test and isolate.
>
> http://techreport.com/news/28473/some-samsung-ssds-may-suffer-from-a-buggy-trim-implementation
>
This is an Intel SSD in a Lenovo Thinkpad X1 Carbon. Trim worked until a
few weeks ago and still works for my small ext4 boot partition (just ran
it to check). I will keep looking for a solution. Thanks!
--
//Christian
next prev parent reply other threads:[~2015-06-17 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 14:18 trim not working and irreparable errors from btrfsck Christian
2015-06-16 21:14 ` Chris Murphy
[not found] ` <55816E7B.5040905@gmail.com>
2015-06-17 14:22 ` Chris Murphy
2015-06-17 14:33 ` Christian
2015-06-17 15:28 ` Chris Murphy
2015-06-17 15:40 ` Christian [this message]
2015-06-17 17:17 ` Austin S Hemmelgarn
2015-06-18 5:25 ` Duncan
2015-08-14 15:11 ` Jeff Mahoney
2015-06-20 14:11 ` Lutz Euler
2015-06-21 7:21 ` Paul Jones
2015-08-13 9:23 ` Marc Joliet
2015-08-13 23:14 ` Chris Murphy
2015-08-14 8:05 ` Marc Joliet
2015-08-14 8:15 ` Marc Joliet
2015-08-14 10:51 ` Paul Jones
2015-06-18 2:20 ` Paul Jones
2015-06-18 4:15 ` Chris Murphy
2015-06-18 4:19 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mls4dj$2oh$1@ger.gmane.org' \
--to=cdysthe@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.