Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1007410

Summary: Segfault while trying to finish pvmove on inactive LV
Product: Red Hat Enterprise Linux 6 Reporter: Peter Rajnoha <prajnoha>
Component: lvm2Assignee: Alasdair Kergon <agk>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: high    
Version: 6.5CC: agk, cmarthal, dwysocha, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, thornber, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.100-3.el6 Doc Type: Bug Fix
Doc Text:
This bug appeared during testing of unreleased version and it has been fixed. No doc text needed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 23:28:26 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:

Description Peter Rajnoha 2013-09-12 12:43:57 UTC
[root@rhel6-a ~]# pvcreate /dev/sda /dev/sdb
  Physical volume "/dev/sda" successfully created
  Physical volume "/dev/sdb" successfully created

[root@rhel6-a ~]# vgcreate vg /dev/sda /dev/sdb
  Volume group "vg" successfully created

[root@rhel6-a ~]# lvcreate -L2g vg /dev/sda
  Logical volume "lvol0" created

[root@rhel6-a ~]# pvmove /dev/sda /dev/sdb
  /dev/sda: Moved: 0.2%
  /dev/sda: Moved: 15.0%

(REBOOT)

The segfault seen at boot while calling vgchange -ay and also when trying to
run the activation directly on command line:

[root@rhel6-a ~]# lvs
  LV      VG       Attr       LSize Pool Origin Data%  Move Log Cpy%Sync Convert
  lv_root VolGroup -wi-ao---- 7.54g                                             
  lv_swap VolGroup -wi-ao---- 1.97g                                             
  lvol0   vg       -wI------- 2.00g                                             
[root@rhel6-a ~]# lvchange -ay vg/lvol0
Segmentation fault


Fixed by:
https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=c0f987949b8a0bbbbe7f06694f59f710a73814da

Comment 2 Nenad Peric 2013-10-01 12:46:45 UTC
Marking verified with:

lvm2-2.02.100-3.el6.x86_64


No segfault encountered with multiple reboots and activations/deactivations.

Comment 3 errata-xmlrpc 2013-11-21 23:28:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1704.html