From: dE <de.techno@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: fdisk and 2048 sectors obsession.
Date: Tue, 28 Oct 2014 20:03:07 +0530 [thread overview]
Message-ID: <544FA923.5080205@gmail.com> (raw)
In-Reply-To: <544F3B20.7090109@gmail.com>
On 10/28/14 12:13, Bruce Dubbs wrote:
> dE wrote:
>> On 10/28/14 00:37, Felix Miata wrote:
>>> dE composed on 2014-10-28 00:13 (UTC+0530):
>>>
>>>> I was learning about GPT when I noticed this behavior of fdisk which I
>>>> never though about before.
>>>> Regardless of the partition table, fdisk always starts the first
>>>> partition at 2048. In reality, the maximum size required by the gap
>>>> between MBR and the 1st partition is a single sector, which's used by
>>>> GRUB 1.5. GPT doesn't need this space at all.
>>>> Then extended partitions too have a gap of 2048 sectors.
>>>> Why this behavior?
>>> 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.
>>
>> 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.
>
> You seem to be overly concerned about the disk space below sector
> 2048. That's a little less than 1M -- less than a floppy disk. In the
> era of $100/TB, does 1M matter?
>
> When formatting a drive, there are several issues to consider. If
> it's a boot drive, then the boot loader needs to go somewhere. Grub
> puts it in sectors 2-63 for MSDOS style partition tables and in a
> separate Grub partition for GPT formatted drives.
>
> Larger hard drives (2T+) require a GPT to access the entire drive.
> They also are formatted internally as 4K sectors. Creating a partition
> that is not aligned with the disk architecture is inefficient.
>
> IMO, all partitions should be aligned on 1MiB boundaries by default
> for either type of partition. It's just easier to understand.
>
> -- Bruce
>
But if fdisk puts it at sector 8 for MBR and sector 40 for GPT, it'll
solve the purpose.
2048 is Windows behavior ported to utils-linux. It's pointless.
next prev parent reply other threads:[~2014-10-28 14:33 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 [this message]
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=544FA923.5080205@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).