util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: dE <de.techno@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: fdisk and 2048 sectors obsession.
Date: Tue, 28 Oct 2014 11:35:57 -0400	[thread overview]
Message-ID: <20141028153557.GA20378@thunk.org> (raw)
In-Reply-To: <544FAE07.6080605@gmail.com>

On Tue, Oct 28, 2014 at 08:23:59PM +0530, dE wrote:
> >Not only that. It was an explicit request from IDEMA. The disk drive and
> >RAID vendors asked all operating system vendors to ensure 1MB alignment
> >by default.
> >
> 
> Ok, it's an IDEMA recommendation. That's why.

One additional reason why it's a good idea is for better compatibility
with drive-managed or host-aware SMR (Shingled Magnetic Recording)
disks, it's a really good idea if partitions are aligned on 256 MiB
boundaries.

And in the future, the hard drive vendors hope to promulgate 32k or
64k native sector size.  If we adopted the suggestion to align new
partitions at 4k after the MBR, it would be disastrous for SMR disks
(some of which will be shipping soon, or may be shipping already but
you might know it, especially for some high-capacity USB attached
storage), and for these larger sector disks.

Or if you are using very low-end flash (i.e., on SD cards) which have
a very primitive FTL, if the partitions aren't aligned on the erase
block, you will also have terrible performance --- and this is true
today.

Given the painful history of how long it took to get OS vendors to
move off of a sector 63 offset (a decade, thanks to Windows XP), it's
not surprising IDEMA has requested that all OS vendors use a 1MB
alignment for partitions going forward.

So I don't think we want to change the default.  If you're so hard up
for space that clawing back that extra 1020k with of disks on a 2T or
6T disk is significant, you can manually adjust the starting offset of
the partition.  But I really don't think it's worth it, at least for
myself....

Cheers,

						- Ted

  reply	other threads:[~2014-10-28 15:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 18:43 fdisk and 2048 sectors obsession dE
2014-10-27 19:07 ` Felix Miata
2014-10-28  3:24   ` dE
2014-10-28  3:55     ` Felix Miata
2014-10-28  4:30       ` dE
2014-10-28  5:53         ` Felix Miata
2014-10-28  7:32           ` Karel Zak
2014-10-28  7:49             ` Felix Miata
2014-10-28  8:48               ` Martin Steigerwald
2014-10-28  8:47     ` Martin Steigerwald
     [not found]     ` <544F3B20.7090109@gmail.com>
2014-10-28 14:33       ` dE
2014-10-28 17:11         ` Linda Walsh
2014-10-29 14:28           ` Dale R. Worley
2014-10-28  7:53 ` Karel Zak
2014-10-28 12:38   ` Martin K. Petersen
2014-10-28 14:53     ` dE
2014-10-28 15:35       ` Theodore Ts'o [this message]
2014-10-29 16:40         ` dE

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=20141028153557.GA20378@thunk.org \
    --to=tytso@mit.edu \
    --cc=de.techno@gmail.com \
    --cc=util-linux@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 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).