Description of problem:
In the latest released version of lvm for Fedora 23 and older versions of lvm you get the following behavior:
# lvresize -L+0B test/lvol0 ; echo $?
New size (1 extents) matches existing size (1 extents)
Run `lvresize --help' for more information.
3
In the latest development tree you get:
# tools/lvm lvresize -L+0B test/lvol0 ; echo $?
0
Using git bisect, I can see this change of behavior was introduced with:
ca878a3426197b629c76e98cfc049948da470cd7 is the first bad commit
commit ca878a3426197b629c76e98cfc049948da470cd7
Author: Zdenek Kabelac <zkabelac>
Date: Tue Jan 19 11:44:11 2016 +0100
cleanup: adjust once
Blivet and others are expecting that a re-size of a LV specifying the same size will indeed fail, please fix.
Description of problem: In the latest released version of lvm for Fedora 23 and older versions of lvm you get the following behavior: # lvresize -L+0B test/lvol0 ; echo $? New size (1 extents) matches existing size (1 extents) Run `lvresize --help' for more information. 3 In the latest development tree you get: # tools/lvm lvresize -L+0B test/lvol0 ; echo $? 0 Using git bisect, I can see this change of behavior was introduced with: ca878a3426197b629c76e98cfc049948da470cd7 is the first bad commit commit ca878a3426197b629c76e98cfc049948da470cd7 Author: Zdenek Kabelac <zkabelac> Date: Tue Jan 19 11:44:11 2016 +0100 cleanup: adjust once Blivet and others are expecting that a re-size of a LV specifying the same size will indeed fail, please fix.