From: "Günter Waller" <g.wal@web.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Samsung 840 EVO
Date: Mon, 04 May 2015 14:38:55 +0200 [thread overview]
Message-ID: <5547685F.7000103@web.de> (raw)
Dear Tejun,
the subject Samsung SSD is having performance issues with "old data"
which Samsung now addresses with a new firmware. As often is the case,
Linux users find it a bit more difficult to apply that fix. However, I
also have a Windows system, so it should be no big deal for me.
But there is also a big concern for Linux users which this FW version
seems to introduce. The link below points to a warning (backed by
others, elsewhere on the web) that fstrim in combination with this FW
will wreck your drive.
http://www.overclock.net/t/1507897/samsung-840-evo-read-speed-drops-on-old-written-data-in-the-drive/2640%23post_23827674
(search for fstrim)
I raised this in a discussion thread of the Ubuntu MATE community and
was pointed to the SSD blacklist that is part of the module
libata-core.c which names you as the maintainer. I wonder if you could
take a look at this issue - maybe you want to add the device to the
blacklist thereafter if need be.
If you find the time and find this worthwhile to investigate I would
appreciate a brief notification of the outcome. For now I am holding
back the FW update.
Best regards
Guenter Waller
next reply other threads:[~2015-05-04 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 12:38 Günter Waller [this message]
2015-05-04 15:28 ` Samsung 840 EVO Martin K. Petersen
2015-05-04 15:49 ` Sven Köhler
2015-05-04 16:21 ` Martin K. Petersen
2015-05-04 16:27 ` Sven Köhler
2015-05-04 16:35 ` Martin K. Petersen
2015-05-04 16:19 ` Günter Waller
2015-05-04 16:24 ` Martin K. Petersen
2015-05-04 16:37 ` Günter Waller
2015-05-04 16:47 ` Martin K. Petersen
2015-05-04 15:45 ` Sven Köhler
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=5547685F.7000103@web.de \
--to=g.wal@web.de \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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.