All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter M. Petrakis" <peter.petrakis@canonical.com>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Is there a reliable way to ID a SSD?
Date: Mon, 03 Jan 2011 14:30:07 -0500	[thread overview]
Message-ID: <4D2223BF.8090901@canonical.com> (raw)
In-Reply-To: <AANLkTimRUqg4cJzV1O1-Cf+KsX6sRjYrz48Ty1-qMX-c@mail.gmail.com>

Hi,

On 12/30/2010 10:58 AM, Greg Freemyer wrote:
> All,
> 
> Per T13/1699-D Revision 4a (from May 2007) word 217 of the identify
> block should be populated with a "1" to identify non-rotating media.
> 
> http://www.t13.org/Documents/UploadedDocuments/docs2007/D1699r4a-ATA8-ACS.pdf
> 
> Does anyone know if that is a reliable field?
> 
> Specifically there are two separate issues:
> 
> 1) Are all devices reporting a 1 in field 217 non-rotating?
> 2) Are all production non-rotating devices populating that field with a 1.
> 
> Is there some other reliable mechanism for identifying a SSD?
> 

Not really, the manufacturer needs to adhere to the spec they're claiming
to honor and we should politely notify them when we find that it's inconsistent.
It's technically a firmware bug if it's ATA-8 and that bit isn't set right.

If you're having trouble identifying SSDs pre ATA-8, you can use this simple
patch I introduced a while back.

http://www.spinics.net/lists/linux-ide/msg38944.html

and blacklist the offending drive into reporting itself as SSD when interrogated
via SCSI.

If you search around, you'll find an earlier thread about quirking SSDs by using
heuristics like search for the word "flash" in the device name and other hints but
the patch set never went anywhere. It's a ugly problem, there's so many devices
out there ahead of the spec that are SSD, with no sure fire way to determine that
they really are. Supporting a full blacklist of them would turn libata-core.c into
a dumping ground for potentially 100s of pre ATA-8 storage devices. I don't think
anyone wants to maintain that.

Peter

  reply	other threads:[~2011-01-03 19:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 15:58 Is there a reliable way to ID a SSD? Greg Freemyer
2011-01-03 19:30 ` Peter M. Petrakis [this message]
2011-01-03 21:24   ` Greg Freemyer
2011-01-03 22:03     ` Peter M. Petrakis
2011-01-03 22:50       ` Greg Freemyer
2011-01-04 15:47         ` Mark Lord
2011-01-04 16:22           ` Greg Freemyer
2011-01-05  0:05         ` Martin K. Petersen
2011-01-06 16:10       ` Jan Ceuleers
     [not found]         ` <AANLkTin1ZjPmbk1M=9-SGStU7zLUozwxX7Ddtu53xNE2@mail.gmail.com>
2011-01-06 18:40           ` Greg Freemyer
2011-01-06 18:55             ` Jeff Garzik
2011-01-06 19:31             ` Martin K. Petersen
2011-01-06 20:11               ` Greg Freemyer
2011-01-06 20:41               ` Jeff Garzik
2011-01-06 21:54                 ` Martin K. Petersen
2011-01-06 19:23         ` Martin K. Petersen
2011-01-06 20:49           ` Jan Ceuleers
2011-01-06 22:02             ` Martin K. Petersen

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=4D2223BF.8090901@canonical.com \
    --to=peter.petrakis@canonical.com \
    --cc=linux-ide@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.