Solved

lvm issue

Posted on 2014-02-18
10
447 Views
Last Modified: 2014-02-25
[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
0
Comment
Question by:ittechlab
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
10 Comments
 
LVL 14

Expert Comment

by:comfortjeanius
ID: 39868759
What does the command produces?

dmesg

Open in new window


or
Plus did you try
 resize2fs -f /dev/myVG/myLV 307200

Open in new window



This comes from this link, " Size in superblock is different from the physical size of the partition"
0
 

Author Comment

by:ittechlab
ID: 39868765
vgcfgrestore[6786] general protection rip:44851f rsp:7fff509c1180 error:0
0
 

Author Comment

by:ittechlab
ID: 39868768
[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
0
Learn by Doing. Anytime. Anywhere.

Do you like to learn by doing?
Our labs and exercises give you the chance to do just that: Learn by performing actions on real environments.

Hands-on, scenario-based labs give you experience on real environments provided by us so you don't have to worry about breaking anything.

 

Author Comment

by:ittechlab
ID: 39868781
[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.
0
 

Author Comment

by:ittechlab
ID: 39870451
[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.
0
 
LVL 14

Expert Comment

by:comfortjeanius
ID: 39870507
Can you check the volume status:

lvs

Open in new window


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
0
 

Author Comment

by:ittechlab
ID: 39870515
[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
0
 

Author Comment

by:ittechlab
ID: 39870536
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?
0
 
LVL 14

Expert Comment

by:comfortjeanius
ID: 39870574
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.
0
 
LVL 14

Accepted Solution

by:
comfortjeanius earned 500 total points
ID: 39870613
If you are trying to remove a disk from the logical volume.....
either to replace the disk or to use the disk as part of a different volume. In order to remove a disk, you must first move the extents on the LVM physical volume to a different disk or set of disks.

Check this link out, "Removing a Disk from a Logical Volume"
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
In part one, we reviewed the prerequisites required for installing SQL Server vNext. In this part we will explore how to install Microsoft's SQL Server on Ubuntu 16.04.
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question