Re: kernel: device-mapper: table: 254:1: adding target device sda1 caused an alignment inconsistency
On Sat, 28 Jul 2018, Rick Thomas wrote:
> > rbthomas@small:~$ lsblk -t
> > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
> > sda 0 4096 33553920 4096 512 1 mq-deadline 60 128 0B
> > `-sda1 0 4096 33553920 4096 512 1 mq-deadline 60 128 0B
> > |-small-swap -1 4096 0 4096 512 1 128 128 32M
> > |-small-root -1 4096 0 4096 512 1 128 128 32M
> > `-small-home -1 4096 0 4096 512 1 128 128 32M
> > mmcblk2 0 512 0 512 512 0 mq-deadline 128 128 0B
> > |-mmcblk2p1 0 512 0 512 512 0 mq-deadline 128 128 0B
> > `-mmcblk2p2 0 512 0 512 512 0 mq-deadline 128 128 0B
> > rbthomas@small:~$
>
> Note the alignment values of “-1” for the lvm entries but not for the GPT partition or the whole disk.
> Why do you suppose that is?
Keep in mind that you *offset*-align the outer container *only*, and then inside
you just keep the size alignment.
So, the above ensures correct use of the partitions even if sda1 is
unaligned.
If you offset-align sda1 to -1, everything inside it should have an offset of
zero to keep the alignment correct.
--
Henrique Holschuh
Reply to: