partition-alignment · shipping · also partition start alignment

Partition alignment

Partition alignment places a partition's starting offset on boundaries appropriate to the storage topology reported by the underlying stack.

An aligned partition does not ensure that every subsequent request has an aligned offset and length. The companion explanation separates partition geometry, individual I/O and persistence.

GPT partition addresses are expressed in logical blocks. Their byte position depends on the logical block size, while alignment depends on the underlying topology; recognizing the partition table alone does not establish alignment. [6]

Relations

related
Advanced Format (4K), Solid-state drive (SSD), Hard disk drive (HDD), Direct I/O, Read-modify-write, Logical sector, Physical sector, 512e emulation, 4Kn native sectors, Minimum I/O size, Optimal I/O size, Alignment offset, GUID Partition Table (GPT)

Advantages

  • Avoids adding a partition-start displacement to otherwise aligned requests. [2]

Limitations

  • Linux exposes device and partition alignment offsets separately from preferred I/O sizes. [3]
  • Unbuffered I/O may also impose buffer-address and request-size requirements. [4]

Citations

  1. Microsoft: Advanced format disk compatibility update, sector formats and alignment issues (accessed 2026-10-12)
  2. Linux 6.12: stable sysfs block ABI, sector sizes and I/O topology (accessed 2026-10-12)
  3. Microsoft: File buffering, alignment and file access requirements (accessed 2026-10-12)
  4. UEFI 2.10, chapter 5: GPT layout, headers and partition entries (accessed 2026-10-21)

Further reading

  1. Partition alignment (accessed 2026-03-26)
  2. Hesela: 512e, 4Kn and alignment: geometry is not durability (accessed 2026-10-12)

JSON: /data/terms/partition-alignment.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Partition alignment. Hesela. 2026-10-21. https://hesela.dev/terms/partition-alignment/