Bug 1167504

Summary: Error in `/usr/sbin/vgextend': free(): invalid pointer
Product: [Fedora] Fedora Reporter: rhbug
Component: lvm2Assignee: Peter Rajnoha <prajnoha>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, msnitzer, prajnoha, prockai, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.98-16.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-13 09:41:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace
none
-vvvv output of the vgextend command none

Description rhbug 2014-11-25 00:10:58 UTC
Created attachment 960972 [details]
backtrace

Description of problem:
vgextend receives SIGABRT. When I try to extend a volumegroup. I does say that what I want to do isn't possible, but right after that it crashed.

Version-Release number of selected component (if applicable):
LVM version:     2.02.98(2) (2012-10-15)
Library version: 1.02.77 (2012-10-15)
Driver version:  4.27.0

How reproducible:
Every time.

Steps to Reproduce:
1. I don't really know since I don't know the exact state of the volume group and the partition I was trying to add.
2.
3.

Actual results:
vgextend said that it can't do that, and subsequently crashed.

Expected results:
My partition to be added to the volumegroup.

Additional info:
The partition I was trying to add is formatted with ext4, and it is named dm-0. Maybe it is already part of the volumegroup like lvextend says (it was my swapspace set up by the installer).

Comment 1 rhbug 2014-11-25 01:50:38 UTC
Created attachment 960990 [details]
-vvvv output of the vgextend command

Comment 2 Peter Rajnoha 2014-11-25 09:12:49 UTC
There were lots and lots of fixes since lvm2 v98 in this area (lvmetad support). We might as well do a rebase for F19.

Comment 3 Peter Rajnoha 2014-11-25 10:14:57 UTC
I've found the exact patch: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=2f1a571c9707d596d7716cec9488e54ba4c0c946

Will backport that one.

Comment 4 Fedora Update System 2014-11-25 10:31:04 UTC
lvm2-2.02.98-16.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/lvm2-2.02.98-16.fc19

Comment 5 Fedora Update System 2014-11-27 08:37:24 UTC
Package lvm2-2.02.98-16.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-16.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-15832/lvm2-2.02.98-16.fc19
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-12-13 09:41:53 UTC
lvm2-2.02.98-16.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.