forked from oVirt/vdsm
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Previously we accepted the current and maximum size of the volume, and computed the next volume size, including one chunk of free space, and ensuring that the size is limited by the volume capacity and qcow2 overhead. This works for auto extending thin volume and for pre extend during replication, but it does not work correctly for internal live merge, when we don't want to add one chunk of free space. It also ugly that in active layer merge we have to lie and call with the maximum required size as the "current" size. Change extend_volume() to accept the new size, moving the responsibility to the caller. The 3 callers were update to compute the size using drive.getNextVolumeSize(). Signed-off-by: Nir Soffer <nsoffer@redhat.com>
- Loading branch information
Showing
3 changed files
with
21 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters