From: Theodore Tso <tytso@mit.edu>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Jim Meyering <jim@meyering.net>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Matthew Wilcox <matthew@wil.cx>,
Ric Wheeler <rwheeler@redhat.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: tools support for non-512 byte sector sizes
Date: Wed, 30 Jul 2008 14:13:52 -0400 [thread overview]
Message-ID: <20080730181351.GA5347@mit.edu> (raw)
In-Reply-To: <20080730172922.GA20191@auslistsprd01.us.dell.com>
On Wed, Jul 30, 2008 at 12:29:22PM -0500, Matt Domsch wrote:
> 2) those that report a 512-byte sector size, but are really a
> 4096-byte size, and the drive does the conversions and
> read/modify/write. T10 and T13 are looking to add commands to
> expose this different underlying physical sector size so the OS
> could be aware of it. This is primarily being driven to mitigate
> any problems that may happen with "legacy" OSs that are not aware
> of the difference.
As usual, the biggest problem will be "legacy" userspace. For
example, most partition tools are still generating legacy partition
tables that look like this:
Disk /dev/sda: 255 heads, 63 sectors, 38913 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 1 0 254 63 121 63 1959867 83
2 00 0 1 122 254 63 619 1959930 8000370 82
3 00 0 1 620 254 63 1023 9960300 615177045 05
4 00 0 0 0 0 0 0 0 0 00
5 00 1 1 620 254 63 1023 63 615176982 8e
Note the starting sector# for the first partition.....
- Ted
next prev parent reply other threads:[~2008-07-30 18:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 17:24 tools support for non-512 byte sector sizes Ric Wheeler
2008-07-29 18:21 ` Alan Cox
2008-07-29 18:55 ` Matthew Wilcox
2008-07-29 21:07 ` Alan Cox
2008-07-29 18:26 ` Matthew Wilcox
2008-07-29 18:37 ` James Bottomley
2008-07-29 18:42 ` Matthew Wilcox
2008-07-29 18:44 ` James Bottomley
2008-07-29 18:50 ` Matthew Wilcox
2008-07-29 19:00 ` James Bottomley
2008-07-29 18:48 ` Martin K. Petersen
2008-07-29 18:54 ` Ric Wheeler
2008-07-29 18:56 ` James Bottomley
2008-07-29 23:41 ` FUJITA Tomonori
2008-07-30 13:51 ` Matt Domsch
2008-07-30 17:16 ` Jim Meyering
2008-07-30 17:29 ` Matt Domsch
2008-07-30 17:24 ` Alan Cox
2008-07-30 18:13 ` Theodore Tso [this message]
2008-07-30 18:28 ` Ric Wheeler
2008-07-30 18:28 ` Ric Wheeler
2008-07-30 18:28 ` Ric Wheeler
2008-07-30 18:45 ` Theodore Tso
2008-08-09 13:21 ` Pavel Machek
2008-08-01 16:11 ` Matthew Wilcox
2008-08-05 16:54 ` Matthew Wilcox
2008-08-05 16:57 ` Matthew Wilcox
2008-08-05 16:57 ` Matt Domsch
2008-07-30 5:51 ` Vladislav Bolkhovitin
2008-07-29 18:41 ` Martin K. Petersen
2008-07-29 21:54 ` Jeff Garzik
2008-07-29 18:43 ` Moore, Eric
2008-07-29 19:03 ` Martin K. Petersen
2008-07-29 19:14 ` Douglas Gilbert
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=20080730181351.GA5347@mit.edu \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Matt_Domsch@dell.com \
--cc=jeff@garzik.org \
--cc=jim@meyering.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthew@wil.cx \
--cc=rwheeler@redhat.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 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.