You are not logged in.
Pages: 1
I understand the alignment issue, but I don't understand why the default alignment is so high at 2048. Wouldn't something like 8 or 16 do just fine, or even 32 or 64 if you really want to plan for the future?
Last edited by dgbaley27 (2012-11-17 01:00:32)
Offline
https://wiki.archlinux.org/index.php/Pa … _Alignment
The key to alignment is partitioning to (at least) the EBS (erase block size) of the SSD.
EBS sizes on most SSDs are 512 KiB, so you need to align to at least 1024 sectors. By aligning to 2048 you can be almost certainly sure that partitions are aligned properly on any SSD.
Also, 1 MiB just looks clean and elegant. There are probably other reasons for such value, unfortunately I don't know about anything more than I said.
Offline
Thanks msthev, I think when my eyes see 512, I tend to think bytes, and missed the KiB.
Offline
I'm the author of GPT fdisk, so I can answer definitively on this one. Basically, msthev is correct; a 1MiB alignment value works well on a wide variety of disks and disk devices -- Advanced Format disks, SSDs, and RAID arrays. Just as important, 1MiB alignment is now pretty much standard -- Microsoft's tools, Apple's Disk Utility, and libparted all use it by default. Sticking with the same alignment policy means that you won't get weird things like little gaps between partitions if you switch between tools when creating partition tables. (Such gaps wouldn't really matter, but people have complained to me about more minor issues.)
Offline
Thank you srs5694 for working on this tool
OpenBSD-current Thinkpad X230, i7-3520M, 16GB CL9 Kingston, Samsung 830 256GB
Contributor: linux-grsec
Offline
Pages: 1