>> I often recommend aligning partitions to 1GiB, also because I
>> like to have 1GiB or so of empty space at the very beginning
>> and end of a drive.
> I'm really curious why do you use such alignment? I can think
> about few reasons, but most practical I think you like to
> slice in gigabyte sizes.
Indeed, and to summarize:
* As mentioned before, I usually leave a chunk of unused space
at the very start and end of a drive. This also because:
- Many head landing accidents happen at the start or end of a
- Free space at the start: sometimes it is useful to have a
few seconds of grace at the start when duplicating a drive
to realize one has mistyped the name, and many partitioning
or booting schemes can use a bit of free space at the start.
Consider XFS and its use of sector 0.
- Free space at the end: many drives have slightly different
sizes, and this can cause problems when for example
rebuilding arrays, or doing backups, and leaving some bit
unused can avoid a lot of trouble.
* Having even sizes for partitions means that it may be easier
to image copy them from one drive to another. I often to do
that. Indeed I usually create partitions of a few "standard"
sizes, usually tailored to fit drives that tend also to come
in fairly standard increments, because drive manufacturers in
each new platter generation usually aim at a fairly standard
factor of improvement. Standard drive sizes tend to be, in
gigabytes: 80 160 250 500 1000 1500 2000 3000. Since 80 and
160 are somewhat old and no longer used, I currently tend to
do partitions in sizes like 230GiB, 460GiB, 920GiB etc. SSDs
have somewhat complicated this.
* On a contemporary drive 1GiB is a rather small fraction of the
capacity of a drive, so why not just align everything to 1GiB,
even if it seems pretty large in absolute terms? And if you
align the first partition to start at 1GiB, and leave free
space at the end, it is farily natural to align everything in
between on 1GiB boundaries.
In this as in many other cases I like to buy myself some extra
degrees of freedom if they are cheap.
Another example I have written about previously is specifying
advisedly chosen 'sunit' and 'swidth' even on non-RAID volumes,
or non-parity RAID setups, not because they really improve
things, but because the cost is minimal and it might come useful
Note: I *really* like to be able to do partition image copies,
because they are so awesomely faster than treewise ones.