[parted-devel] mkpart: use same end and start value for two partitions?

[Oliver Smith]

Hi,

I wonder if I'm using "parted mkpart" right. As I understand, one should 
be able to use the same end value and start value for two partitions 
that follow each other.

In an automated job that has built over 1000 images, this worked every 
time until recently where I found:

$ parted -s /dev/install mkpart primary ext2 4096s 256M
$ parted -s /dev/install mkpart primary 256M 3313M
$ parted -s /dev/install mkpart primary 3313M 100%
Error: You requested a partition from 3313MB to 7207MB (sectors 
6470703..14075903).
The closest location we can manage is 3314MB to 7207MB (sectors 
6471680..14075903).

For this automated job, the size of the second partition varies.

Distribution: Alpine Linux
Version: parted 3.5 (doesn't necessarily seem related to upgrading to 
3.5 though, that upgrade was done in May, the job started failing in 
June and ran a lot of times between that timeframe. Or maybe it is a 
combination of the 3.5 upgrade and hitting values that it can't handle?)

Full job output:
https://builds.sr.ht/~postmarketos/job/801253#task-img_installer-791


Is this a bug in parted or am I using it wrong?


PS: reading documentation I've understood now that it would probably be 
smarter to align to 4 MiB blocks. But that's a different topic.

Best,
Oliver