From: Theodore Tso <tytso@mit.edu>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
Jim Meyering <jim@meyering.net>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Matthew Wilcox <matthew@wil.cx>,
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:45:51 -0400 [thread overview]
Message-ID: <20080730184551.GB5347@mit.edu> (raw)
In-Reply-To: <4890B2BC.10808@redhat.com>
On Wed, Jul 30, 2008 at 02:28:12PM -0400, Ric Wheeler wrote:
> If I remember correctly, the MS Vista new alignment for data partitions
> is on a 0 offset, 1MB aligned boundary. The support for 4096 byte
> sectors is only for data partitions (not boot).
>
> Array vendors, who consume a fair amount of drives, are most likely more
> friendly to native 4k drives. The big fear from disk vendors is getting
> a wave of returns from Best Buy, etc when people go and plug in a new,
> native 4k drive into an old box....
Or a new box running XP, either via the Dell "upgrade to XP" program,
or from a corporate I/T load[1]. :-)
[1] http://www.theinquirer.net/gb/inquirer/news/2008/06/23/intel-dumps-vista
More to the point for Linux, are *our* partition table programs (i.e.,
fdisk, cfdisk, et. al) fixed with better defaults in upstream, and
what are the upcoming enterprise distributions going to ship with?
Since that's what a large number of Linux customers will end up using
for the next 3-5 years....
- Ted
next prev parent reply other threads:[~2008-07-30 18:47 UTC|newest]
Thread overview: 32+ 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
2008-07-30 18:28 ` Ric Wheeler
2008-07-30 18:45 ` Theodore Tso [this message]
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=20080730184551.GB5347@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 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).