From: Matthew Wilcox <matthew@wil.cx>
To: Theodore Tso <tytso@mit.edu>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
sandeen@redhat.com
Subject: Re: ATA support for 4k sector size
Date: Wed, 25 Feb 2009 20:07:35 -0700 [thread overview]
Message-ID: <20090226030735.GA16891@parisc-linux.org> (raw)
In-Reply-To: <20090226025043.GJ1363@mit.edu>
On Wed, Feb 25, 2009 at 09:50:43PM -0500, Theodore Tso wrote:
> On Wed, Feb 25, 2009 at 06:27:18PM -0500, Martin K. Petersen wrote:
> > Because of 63-sector legacy problems a bunch of ATA vendors will
> > initially ship 512/4096 drives that are not naturally aligned.
> > I.e. logical sector 63 will be aligned on a 4KB hardware sector
> > boundary to overcome the misaligned default partitioning.
>
> Are we *sure* that this is what they plan to be doing? Is there a way
> we can query the hardware to find out for sure what drives are doing
> what?
The drive I have that's pretending to be a 512/4k drive reports this:
$ sudo sg_readcap -l /dev/sdc
Read Capacity results:
Protection: prot_en=0, p_type=0
Last logical block address=625142447 (0x2542eaaf), Number of logical blocks=625142448
Logical block length=512 bytes
Logical blocks per physical block=3 (log base 2) [actual=8]
Lowest aligned logical block address=0
Hence:
Device size: 320072933376 bytes, 305245.3 MiB, 320.07 GB
This disagrees with Martin's assertion.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-02-26 3:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 22:24 ATA support for 4k sector size Matthew Wilcox
2009-02-25 22:24 ` [PATCH 1/2] ata: Define new commands from ATA8 Matthew Wilcox
2009-02-25 22:24 ` [PATCH 2/2] ata: Add support for Long Logical Sectors and Long Physical Sectors Matthew Wilcox
2009-02-25 22:53 ` ATA support for 4k sector size H. Peter Anvin
2009-02-25 23:27 ` Martin K. Petersen
2009-02-25 23:33 ` H. Peter Anvin
2009-02-25 23:51 ` Martin K. Petersen
2009-02-26 12:43 ` Karel Zak
2009-02-26 15:17 ` H. Peter Anvin
2009-02-25 23:42 ` H. Peter Anvin
2009-02-25 23:55 ` Martin K. Petersen
2009-02-25 23:57 ` H. Peter Anvin
2009-02-26 0:07 ` Martin K. Petersen
2009-02-26 0:10 ` H. Peter Anvin
2009-02-26 0:17 ` Martin K. Petersen
2009-02-25 23:49 ` david
2009-02-26 0:04 ` Martin K. Petersen
2009-02-26 0:13 ` david
2009-02-26 0:20 ` Martin K. Petersen
2009-02-26 2:50 ` Theodore Tso
2009-02-26 3:05 ` Martin K. Petersen
2009-02-26 3:07 ` Matthew Wilcox [this message]
2009-02-26 3:23 ` Martin K. Petersen
2009-12-11 7:05 ` James Andrewartha
2009-12-11 7:26 ` H. Peter Anvin
2009-12-11 7:32 ` Martin K. Petersen
2009-02-26 5:16 ` Martin K. Petersen
2009-02-26 12:36 ` Matthew Wilcox
2009-02-26 15:32 ` H. Peter Anvin
2009-02-26 20:35 ` Martin K. Petersen
2009-02-26 21:02 ` H. Peter Anvin
2009-03-16 14:51 ` Greg Freemyer
2009-03-16 16:27 ` H. Peter Anvin
2009-03-16 17:37 ` Greg Freemyer
2009-03-16 18:11 ` H. Peter Anvin
2009-03-22 1:20 ` Bill Davidsen
2009-03-18 14:33 ` James Bottomley
2009-02-26 18:22 ` hdparm-9.12 released Mark Lord
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=20090226030735.GA16891@parisc-linux.org \
--to=matthew@wil.cx \
--cc=hpa@zytor.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).