Bug 1312091 - lvresize is not exiting with error when re-sizing LV to same size
lvresize is not exiting with error when re-sizing LV to same size
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Zdenek Kabelac
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-25 12:28 EST by Tony Asleson
Modified: 2016-02-29 05:58 EST (History)
12 users (show)

See Also:
Fixed In Version: lvm2-2.02.144-1.fc25
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-29 05:58:47 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tony Asleson 2016-02-25 12:28:57 EST
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@redhat.com>
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.
Comment 1 Zdenek Kabelac 2016-02-25 17:41:12 EST
Yep - commit missed to port more piece from my snapshot resize in-devel patch.

Fixed by explicit validation of sizes args:

https://www.redhat.com/archives/lvm-devel/2016-February/msg00163.html

Note You need to log in before you can comment on or make changes to this bug.