Currently existing partions are scaled all by the same factor. The logic should be more intelligent to move partition boundaries when necessary.
For instance, if a device has 2 partitions with 75 and 25 GB. Each is filled with 20 GB. Then 40 GB are in use and it should be no problem to clone this disk to a 50GB disk. But reducing 75 by half and 25 by half will later on produce an error because the second partition is only 12.5GB. And that is too less for 20GB!
Possible options:
Add up all used space of all partitions and subscract from smaller destination size. Create distirbution factor by:
putting each used value of each partition in relation to total used space
putting each original partition size in relation to original disk size
dividing free space by the number of partitions
Of course, boot, efi and the like should be excluded.
Currently existing partions are scaled all by the same factor. The logic should be more intelligent to move partition boundaries when necessary.
For instance, if a device has 2 partitions with 75 and 25 GB. Each is filled with 20 GB. Then 40 GB are in use and it should be no problem to clone this disk to a 50GB disk. But reducing 75 by half and 25 by half will later on produce an error because the second partition is only 12.5GB. And that is too less for 20GB!
Possible options: Add up all used space of all partitions and subscract from smaller destination size. Create distirbution factor by:
Of course, boot, efi and the like should be excluded.