From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Joshua Scoggins <theoretically.x64@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Arun <engineerarun@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Detection of Advanced Format drives
Date: Mon, 26 Sep 2011 17:01:42 -0400 [thread overview]
Message-ID: <yq1ehz3f26h.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAK3HsqvkpEiDWcCP_+eO0va4+io7pVV-aWCzQ1=DdpPi_jxy6g@mail.gmail.com> (Joshua Scoggins's message of "Mon, 26 Sep 2011 12:48:46 -0700")
>>>>> "Joshua" == Joshua Scoggins <theoretically.x64@gmail.com> writes:
Joshua> Keep in mind that some AF drives will not report their actual
Joshua> sector sizes. I have this issue with the WD AV-25 series. This
Joshua> is to provide compatibility with older operating systems that
Joshua> don't support AF drives. These are called generation 1
Joshua> devices. Newer drives will directly report their sector size as
Joshua> 4096 through the drive identify data older ones will say 512.
AF drives continue to report a logical block size of 512. There's an
additional parameter in IDENTIFY DEVICE that describes the physical
block size. Legacy operating systems do not check the physical block
size parameter. Linux does, and will bubble this additional information
up the stack.
There have been a few attempts at switching ATA drives over to 4KB
logical blocks as well. We are ready. However, both boot and legacy OS
compatibility concerns make this a bit of an uphill battle.
As you mention there's one vendor that pretty consistently gets their
physical block size reporting wrong. We've pointed this out to them many
times. Apparently it's been fixed with the latest green drive
firmware...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2011-09-26 21:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 9:55 Detection of Advanced Format drives Arun
2011-09-26 10:15 ` Alan Cox
2011-09-26 19:48 ` Joshua Scoggins
2011-09-26 20:09 ` Mike Snitzer
2011-09-27 17:59 ` Joshua Scoggins
2011-09-27 18:36 ` Arun
2011-09-27 18:59 ` Martin K. Petersen
2011-09-27 19:18 ` Arun
2011-09-27 20:10 ` Mark Knecht
2011-09-27 21:12 ` Arun
2011-09-27 21:44 ` Martin K. Petersen
2011-09-28 1:23 ` NamJae Jeon
[not found] ` <CANLaLhagmNFFrNxC88cyPqsx_j+-Y-WaAUCQpkR57z264Bn6Vw@mail.gmail.com>
2012-02-16 19:14 ` Martin K. Petersen
2011-09-26 21:01 ` Martin K. Petersen [this message]
2011-09-26 21:03 ` 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=yq1ehz3f26h.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=engineerarun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=theoretically.x64@gmail.com \
/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