What is the point of specifying a size if it is then ignored?
Seems pointless. How do you create an image of specified size?
If you want free space added after the shrink, specify 'added space for incremental'.
I don't want to add space. I could of course do a backup, ascertain the arbitrary size then calculate how much I want to add and make a new image.
With a new OS I know how big it is likely to grow. I want to create an image of the expected size. I only need to create new image because the size of boot partition changed.
The goal of image-backup is to create a backup which results in the smallest image file possible.
In nearly all cases, it's not necessary to specify an 'inital size'. image-backup will automatically compute an 'inital size' by adding 20% to the used space reported by df. In very rare cases, this may not be adequate and the backup will fail due to the image file not being of sufficient size, so the option to specify an explicit 'initial size' is provided. In all cases, the image file is shrunk to the smallest size possible when the backup is complete. If you intend to incrementally update the image file, then 'added space for incremental' can be specified which will be added after the image file is shrunk.
The fact that the size of your boot partition has changed should not be of concern. Are you encountering an error when creating a new backup with the latest image-backup?
Statistics: Posted by RonR — Wed Feb 21, 2024 9:47 pm