Bug 673484

Summary: vgcfgrestore not working properly
Product: Red Hat Enterprise Linux 5 Reporter: Linux engineering teams - Veritas <linux26port>
Component: lvm2Assignee: Milan Broz <mbroz>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Marthaler <cmarthal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.4CC: agk, bmarzins, dwysocha, heinzm, jbrassow, joe.thornber, mbroz, prajnoha, prockai, pvrabec
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.74-5.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-22 13:28:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
I have attached the configuration file. none

Description Linux engineering teams - Veritas 2011-01-28 11:41:50 UTC
Created attachment 475789 [details]
I have attached the configuration file.

Description of problem: vgcfgrestore not working properly and throwing error message having backtrace.

Version-Release number of selected component (if applicable):
OS details : Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Kernel version :2.6.18-164.el5
LVM version : 
 LVM version:     2.02.46-RHEL5 (2009-06-18)
 Library version: 1.02.32 (2009-05-21)
 Driver version:  4.11.5

How reproducible:
 Easily reproducible.

Steps to Reproduce:
1. create a pv using pvcreate command.
       create a vg using vgcreate command.
       create a logical volume using lvcreate command.
2. take a backup using vgcfgbackup command.
e.g: #vgcfgbackup vg
where vg is a vg name
3. restore the backup using vgcfgrestore command.
e.g #vgcfgrestore -f /etc/lvm/backup/vg -n vg /dev/sdf

  
Actual results:
vgcfgrestore not working properly and throwing error message having backtrace.


Expected results:
vgcfgrestore should able to restore the configuration when the backup is taken properly using the  vgcfgbackup command.

Additional info:
The complete error log is given below:
-----------8<------------------------

# vgcfgrestore -f /etc/lvm/backup/vg -n vg /dev/sdf
  Internal error: pool_free asked to free pointer not in pool
  '/etc/lvm/backup/vg' does not contain volume group 'sdf'.
  Restore failed.
*** glibc detected *** vgcfgrestore: double free or corruption (!prev): 0x0000000006536b50 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3ab74722ef]
/lib64/libc.so.6(cfree+0x4b)[0x3ab747273b]
/lib64/libdevmapper.so.1.02(dm_pool_destroy+0x29)[0x3ab780cb19]
vgcfgrestore(destroy_toolcontext+0x5b)[0x42f1cb]
vgcfgrestore(lvm2_main+0x2c5)[0x418ac5]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3ab741d994]
vgcfgrestore[0x40da69]
======= Memory map: ========
00400000-00493000 r-xp 00000000 08:01 642507                             /usr/sbin/lvm
00693000-00699000 rw-p 00093000 08:01 642507                             /usr/sbin/lvm
00699000-006a1000 rw-p 00699000 00:00 0
00898000-0089d000 rw-p 00098000 08:01 642507                             /usr/sbin/lvm
0650c000-0654e000 rw-p 0650c000 00:00 0                                  [heap]
3ab7000000-3ab701c000 r-xp 00000000 08:01 1737000                        /lib64/ld-2.5.so
3ab721b000-3ab721c000 r--p 0001b000 08:01 1737000                        /lib64/ld-2.5.so
3ab721c000-3ab721d000 rw-p 0001c000 08:01 1737000                        /lib64/ld-2.5.so
3ab7400000-3ab754d000 r-xp 00000000 08:01 1737001                        /lib64/libc-2.5.so
3ab754d000-3ab774d000 ---p 0014d000 08:01 1737001                        /lib64/libc-2.5.so
3ab774d000-3ab7751000 r--p 0014d000 08:01 1737001                        /lib64/libc-2.5.so
3ab7751000-3ab7752000 rw-p 00151000 08:01 1737001                        /lib64/libc-2.5.so
3ab7752000-3ab7757000 rw-p 3ab7752000 00:00 0
3ab7800000-3ab7815000 r-xp 00000000 08:01 1737029                        /lib64/libdevmapper.so.1.02
3ab7815000-3ab7a15000 ---p 00015000 08:01 1737029                        /lib64/libdevmapper.so.1.02
3ab7a15000-3ab7a17000 rw-p 00015000 08:01 1737029                        /lib64/libdevmapper.so.1.02
3ab7c00000-3ab7c02000 r-xp 00000000 08:01 1737002                        /lib64/libdl-2.5.so
3ab7c02000-3ab7e02000 ---p 00002000 08:01 1737002                        /lib64/libdl-2.5.so
3ab7e02000-3ab7e03000 r--p 00002000 08:01 1737002                        /lib64/libdl-2.5.so
3ab7e03000-3ab7e04000 rw-p 00003000 08:01 1737002                        /lib64/libdl-2.5.so
3ab8000000-3ab8016000 r-xp 00000000 08:01 1737007                        /lib64/libpthread-2.5.so
3ab8016000-3ab8215000 ---p 00016000 08:01 1737007                        /lib64/libpthread-2.5.so
3ab8215000-3ab8216000 r--p 00015000 08:01 1737007                        /lib64/libpthread-2.5.so
3ab8216000-3ab8217000 rw-p 00016000 08:01 1737007                        /lib64/libpthread-2.5.so
3ab8217000-3ab821b000 rw-p 3ab8217000 00:00 0
3ab8400000-3ab8407000 r-xp 00000000 08:01 1737010                        /lib64/librt-2.5.so
3ab8407000-3ab8607000 ---p 00007000 08:01 1737010                        /lib64/librt-2.5.so
3ab8607000-3ab8608000 r--p 00007000 08:01 1737010                        /lib64/librt-2.5.so
3ab8608000-3ab8609000 rw-p 00008000 08:01 1737010                        /lib64/librt-2.5.so
3ab8800000-3ab8835000 r-xp 00000000 08:01 644232                         /usr/lib64/libreadline.so.5.1
3ab8835000-3ab8a34000 ---p 00035000 08:01 644232                         /usr/lib64/libreadline.so.5.1
3ab8a34000-3ab8a3c000 rw-p 00034000 08:01 644232                         /usr/lib64/libreadline.so.5.1
3ab8a3c000-3ab8a3d000 rw-p 3ab8a3c000 00:00 0
3ab8c00000-3ab8c3b000 r-xp 00000000 08:01 1737020                        /lib64/libsepol.so.1
3ab8c3b000-3ab8e3b000 ---p 0003b000 08:01 1737020                        /lib64/libsepol.so.1
3ab8e3b000-3ab8e3c000 rw-p 0003b000 08:01 1737020                        /lib64/libsepol.so.1
3ab8e3c000-3ab8e46000 rw-p 3ab8e3c000 00:00 0
3ab9000000-3ab9015000 r-xp 00000000 08:01 1737021                        /lib64/libselinux.so.1
3ab9015000-3ab9215000 ---p 00015000 08:01 1737021                        /lib64/libselinux.so.1
3ab9215000-3ab9217000 rw-p 00015000 08:01 1737021                        /lib64/libselinux.so.1
3ab9217000-3ab9218000 rw-p 3ab9217000 00:00 0
3ab9400000-3ab9404000 r-xp 00000000 08:01 1736889                        /lib64/libdevmapper-event.so.1.02
3ab9404000-3ab9603000 ---p 00004000 08:01 1736889                        /lib64/libdevmapper-event.so.1.02
3ab9603000-3ab9604000 rw-p 00003000 08:01 1736889                        /lib64/libdevmapper-event.so.1.02
3ac9200000-3ac920d000 r-xp 00000000 08:01 1737016                        /lib64/libgcc_s-4.1.2-20080825.so.1
3ac920d000-3ac940d000 ---p 0000d000 08:01 1737016                        /lib64/libgcc_s-4.1.2-20080825.so.1
3ac940d000-3ac940e000 rw-p 0000d000 08:01 1737016                        /lib64/libgcc_s-4.1.2-20080825.so.1
3ac9e00000-3ac9e4f000 r-xp 00000000 08:01 642499                         /usr/lib64/libncurses.so.5.5
3ac9e4f000-3aca04e000 ---p 0004f000 08:01 642499                         /usr/lib64/libncurses.so.5.5
3aca04e000-3aca05c000 rw-p 0004e000 08:01 642499                         /usr/lib64/libncurses.so.5.5
3aca05c000-3aca05d000 rw-p 3aca05c000 00:00 0
2b34f8bf5000-2b34f8bf6000 rw-p 2b34f8bf5000 00:00 0
2b34f8c04000-2b34f8c0a000 rw-p 2b34f8c04000 00:00 0
2b34f8c0a000-2b34fc1df000 r--p 00000000 08:01 626639                     /usr/lib/locale/locale-archive
2b34fc1df000-2b34fc1e6000 r--s 00000000 08:01 723050                     /usr/lib64/gconv/gconv-modules.cache
7fffe46da000-7fffe46ef000 rw-p 7ffffffea000 00:00 0                      [stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0                  [vdso]
Aborted
#

-----------8<------------------------

Comment 1 Milan Broz 2011-01-28 12:13:22 UTC
*** Bug 673481 has been marked as a duplicate of this bug. ***

Comment 2 Milan Broz 2011-01-28 12:19:05 UTC
Please update to RHEL5.6 version (lvm2-2.02.74-5.el5.x86_64), this one bug should be already fixed.

Does that update that fixes the problem for you?

Comment 3 Milan Broz 2011-03-22 13:28:50 UTC
No response for two months, closing this as fixed in current release.

If you can reproduce it with current version, please reopen this bug, thanks.