util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dE <de.techno@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: fdisk and 2048 sectors obsession.
Date: Tue, 28 Oct 2014 10:00:42 +0530	[thread overview]
Message-ID: <544F1BF2.3040203@gmail.com> (raw)
In-Reply-To: <544F13CD.8000502@earthlink.net>

On 10/28/14 09:25, Felix Miata wrote:
> dE composed on 2014-10-28 08:54 (UTC+0530):
>
>> Felix Miata wrote:
>>> http://www.seagate.com/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/
>>> may provide some insight WRT performance issues ensuing from other start
>>> sector selections.
>> But that works even with multiples of 8. So we can start from sector 8
>> in MBR and 40 in GPT.
> OK, as long as you know you'll never need a bootloader or other boot-time
> software that requires the "wasted" space between MBR and first partition
> sector. It seems M$ for Vista picked 2048 to reserve plenty of space for such
> a *possibility* (not necessarily expectation), so for compat reasons and
> other[1], other tools, including fdisk, decided to do the same at least by
> default.
>
> I've created partitions starting at sector 0x400 on 4k disks with no problems
> observed.
>
>> Also I'm pretty sure fdisk uses 2048 even with -b 4096, but
>> unfortunately I get --
>> *** Error in `fdisk': malloc(): memory corruption: 0x0000000002507330 ***
>>    with that switch.
> Bug somewhere?
>
> [1]
> http://www.anchor.com.au/blog/2012/10/the-difference-between-booting-mbr-and-gpt-with-grub/

Yeah, I'll file that bug.

But I also think this fdisk 2048 behavior should be removed now or at 
least provide a switch for the same and document this in the man page.

  reply	other threads:[~2014-10-28  4:31 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 [this message]
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
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=544F1BF2.3040203@gmail.com \
    --to=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).