ittechlab
asked on
lvm issue
[root@rhel5 archive]# e2fsck -f /dev/myVG/myLV
e2fsck 1.39 (29-May-2006)
The filesystem size (according to the superblock) is 569344 blocks
The physical size of the device is 307200 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
how do i fix this
e2fsck 1.39 (29-May-2006)
The filesystem size (according to the superblock) is 569344 blocks
The physical size of the device is 307200 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
how do i fix this
ASKER
vgcfgrestore[6786] general protection rip:44851f rsp:7fff509c1180 error:0
ASKER
[root@rhel5 archive]# resize2fs -f /dev/myVG/myLV 307200
resize2fs 1.39 (29-May-2006)
Resizing the filesystem on /dev/myVG/myLV to 307200 (4k) blocks.
resize2fs: Can't read an block bitmap while trying to resize /dev/myVG/myLV
resize2fs 1.39 (29-May-2006)
Resizing the filesystem on /dev/myVG/myLV to 307200 (4k) blocks.
resize2fs: Can't read an block bitmap while trying to resize /dev/myVG/myLV
ASKER
[root@rhel5 archive]# ll
total 80
-rw------- 1 root root 842 Feb 18 05:55 myVG_00000-913743800.vg
-rw------- 1 root root 847 Feb 18 05:56 myVG_00001-490127411.vg
-rw------- 1 root root 1180 Feb 18 06:44 myVG_00002-1799914869.vg
-rw------- 1 root root 1183 Feb 18 09:17 myVG_00003-1282895976.vg
-rw------- 1 root root 1157 Feb 18 11:17 myVG_00004-508832436.vg
-rw------- 1 root root 1157 Feb 18 11:17 myVG_00005-1913399351.vg
-rw------- 1 root root 1186 Feb 18 11:32 myVG_00006-503181047.vg
-rw------- 1 root root 1186 Feb 18 11:34 myVG_00007-2029148209.vg
-rw------- 1 root root 1183 Feb 18 11:59 myVG_00008-2110559607.vg
I tried to restore previous archive. still i am getting the same issue.
total 80
-rw------- 1 root root 842 Feb 18 05:55 myVG_00000-913743800.vg
-rw------- 1 root root 847 Feb 18 05:56 myVG_00001-490127411.vg
-rw------- 1 root root 1180 Feb 18 06:44 myVG_00002-1799914869.vg
-rw------- 1 root root 1183 Feb 18 09:17 myVG_00003-1282895976.vg
-rw------- 1 root root 1157 Feb 18 11:17 myVG_00004-508832436.vg
-rw------- 1 root root 1157 Feb 18 11:17 myVG_00005-1913399351.vg
-rw------- 1 root root 1186 Feb 18 11:32 myVG_00006-503181047.vg
-rw------- 1 root root 1186 Feb 18 11:34 myVG_00007-2029148209.vg
-rw------- 1 root root 1183 Feb 18 11:59 myVG_00008-2110559607.vg
I tried to restore previous archive. still i am getting the same issue.
ASKER
[root@rhel5 /]# vgremove myVG
Do you really want to remove volume group "myVG" containing 1 logical volumes? [y/n]: y
Do you really want to remove active logical volume myLV? [y/n]: y
Unable to deactivate open myVG-myLV-real (253:2)
Unable to deactivate logical volume "myLV"
why i am unable to remove the VG.
Do you really want to remove volume group "myVG" containing 1 logical volumes? [y/n]: y
Do you really want to remove active logical volume myLV? [y/n]: y
Unable to deactivate open myVG-myLV-real (253:2)
Unable to deactivate logical volume "myLV"
why i am unable to remove the VG.
Can you check the volume status:
Plus make sure......
Check this link, "Why can’t I remove a Linux logical volume? and Cannot Deactivate LVM Logical volume
lvs
Plus make sure......
There is no other indication that the LV or VG is open or in use. The 'df ' command reports no mounted filesystems. Neither 'fuser ' nor 'lsof ' report any open files related to this LV.
Check this link, "Why can’t I remove a Linux logical volume? and Cannot Deactivate LVM Logical volume
ASKER
[root@rhel5 src]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 owi-ao 27.91G
LogVol01 VolGroup00 -wi-ao 1.97G
rootsnap VolGroup00 swi-a- 512.00M LogVol00 95.50
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 owi-ao 27.91G
LogVol01 VolGroup00 -wi-ao 1.97G
rootsnap VolGroup00 swi-a- 512.00M LogVol00 95.50
ASKER
I am trying remove disk
[root@rhel5 src]# dmsetup ls
myVG-myLV-real (253, 2)
VolGroup00-LogVol00-real (253, 7)
VolGroup00-rootsnap-cow (253, 8)
myVG-mylvbackup (253, 5)
VolGroup00-LogVol01 (253, 1)
VolGroup00-LogVol00 (253, 0)
myVG-mylvbackup-cow (253, 4)
VolGroup00-rootsnap (253, 6)
[root@rhel5 src]# pvremove /dev/sdb
Can't open /dev/sdb exclusively - not removing. Mounted filesystem?
[root@rhel5 src]# dmsetup ls
myVG-myLV-real (253, 2)
VolGroup00-LogVol00-real (253, 7)
VolGroup00-rootsnap-cow (253, 8)
myVG-mylvbackup (253, 5)
VolGroup00-LogVol01 (253, 1)
VolGroup00-LogVol00 (253, 0)
myVG-mylvbackup-cow (253, 4)
VolGroup00-rootsnap (253, 6)
[root@rhel5 src]# pvremove /dev/sdb
Can't open /dev/sdb exclusively - not removing. Mounted filesystem?
To remove an inactive logical volume, use the lvremove command. You must close a logical volume with the umount command before it can be removed. In addition, in a clustered environment you must deactivate a logical volume before it can be removed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Open in new window
or
Plus did you try
Open in new window
This comes from this link, " Size in superblock is different from the physical size of the partition"