From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: discard synchronous on most SSDs?
Date: Sat, 15 Mar 2014 15:06:25 +1100 [thread overview]
Message-ID: <1908923.tvpl1fFKJ5@quad> (raw)
In-Reply-To: <5289248.oqpgSKG6td@quad>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
On Fri, 14 Mar 2014 06:33:24 PM Chris Samuel wrote:
> I *think* you want smartctl -i instead, and look for the field that says
> something like:
>
> ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3
Late night, cut and pasted the wrong line of output, mine says:
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Of course that's what the drive is reporting it supports, I'm not sure whether
that's the result of what has been negotiated between the controller and drive
or purely what the drive supports.
To get more information from smartctl you can use the --identify=wb option
instead of -i and that should give you a lot more detail about what then
drives claims to (and not to) support. On the version in Kubuntu 13.10
(6.1+svn3812-1) it only reports 3 things regarding TRIM for my drives.
chris@quad:/tmp$ sudo smartctl --identify=wb -d sat /dev/sdb | egrep -i 'trim|
discard'
69 14 1 Deterministic data after trim supported
69 5 0 Trimmed LBA range(s) returning zeroed data supported
169 0 1 Trim bit in DATA SET MANAGEMENT command supported
I'm currently doing a git clone of their SVN repo to see if there's any new
functionality that will gather any more information.
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2014-03-15 4:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 7:48 Massive BTRFS performance degradation KC
2014-03-09 8:17 ` Swâmi Petaramesh
2014-03-09 10:01 ` Martin Steigerwald
2014-03-09 10:23 ` Swâmi Petaramesh
2014-03-09 11:33 ` Hugo Mills
2014-03-09 11:54 ` Martin Steigerwald
2014-03-09 12:10 ` Swâmi Petaramesh
2014-03-09 17:14 ` boris
2014-03-14 2:11 ` discard synchronous on most SSDs? Marc MERLIN
2014-03-14 3:39 ` Chris Murphy
2014-03-14 5:17 ` Marc MERLIN
2014-03-14 7:33 ` Chris Samuel
2014-03-14 19:26 ` Marc MERLIN
2014-03-14 19:57 ` Martin K. Petersen
2014-03-14 20:46 ` Holger Hoffstätte
2014-03-15 4:21 ` Marc MERLIN
2014-03-15 9:38 ` Holger Hoffstätte
2014-03-15 5:25 ` Chris Samuel
2014-03-15 6:48 ` Chris Samuel
2014-03-15 11:26 ` Duncan
2014-03-15 22:48 ` Chris Samuel
2014-03-16 6:06 ` Marc MERLIN
2014-03-16 17:09 ` Chris Murphy
2014-03-16 16:22 ` Martin K. Petersen
2014-03-16 17:50 ` Marc MERLIN
2014-03-15 4:06 ` Chris Samuel [this message]
2014-03-16 16:07 ` Martin K. Petersen
2014-03-14 12:07 ` Duncan
2014-03-14 21:44 ` Chris Murphy
2014-03-14 7:27 ` Chris Samuel
2014-03-09 17:36 ` Massive BTRFS performance degradation Austin S Hemmelgarn
2014-03-09 18:55 ` Tobias Holst
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=1908923.tvpl1fFKJ5@quad \
--to=chris@csamuel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox