*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706
Is this the same Problem as described there at https://blog.algolia.com
/when-solid-state-drives-are-not-that-solid/ ?
This does affect the 850 EVO also, not just PRO.
Well, the 'bugfix' for 3.16.0-43.58 is there, but somehow the Kernel does not
say 'disabling queued TRIM support'
I currently get 'failed to get NCQ Send/Recv Log Emask 0x1'.
Also I am a bit confused, while it may be another issue only i face,
since the system currently should be 14.04.2 with an lts-utopic kernel,
but the latest kernel uname -a reports, right after an upgrade:
Linux .... 3.16.0-43-generic #58~14.04.1-Ubuntu SMP Mon Jun 22 10:21:20
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
This looks somewhat old by the stated date. Why does aptitude update &&
aptitude dist-upgrade not upgrade to the Version with the 'bugfix', and
why does the Version number indicate a match to the Version with the
'bugfix'?
cat /sys/block/sda/device/queue_depth does report 31
Offtopic:
Does anyone work on detecting or scanning at a low-level (dm, logical
volume manager, file-system) for 512 sized and zeroed areas at
suspicious places, maybe even telling the maybe corrupted filename?
Actually the information I found about fstrim and the real inner
workings in combination with volume managers etc. is hard to find.
I would welcome if someone would pick up on the tests that algolia
published on github to build some stress tests for ssd in general.
Does it zero out 'random' blocks only when it's under some 'heavy load',
or just always?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1449005
Title:
trim does not work with Samsung 840 EVO after firmware update
(EXT0DB6Q)
Status in fstrim package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in fstrim source package in Trusty:
Invalid
Status in linux source package in Trusty:
Fix Released
Status in fstrim source package in Utopic:
Invalid
Status in linux source package in Utopic:
Fix Released
Status in fstrim source package in Vivid:
Invalid
Status in linux source package in Vivid:
Fix Released
Bug description:
Hi,
after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the
fstream command doesn't work anymore. Besides, there are a lot of file system
errors and "bad sectors" reports. The problem is certainly caused by Samsung's
firmware but I reported it as a bug because in Windows TRIM works normally
after the upgrade. I have attached an image uploaded by a user who is
experiencing the same problem. If you execute the command "sudo fstrim /" the
console gets stuck. If you add that command in rc.local the boot is
compromised. I really hope this problem could be solved.
Thanks
===
break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a
break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
