Inconsistent LVM / LVM2 data

asked 2016-03-13 07:00:13 -0500

pja
96 ●2 ●5 ●11

Hi,

I have a Fedora 23 system and I run LVM for the / (root) partition and for the /home (home) partition so as to be able to allocate more or less space based on available physical hard disk space I have. I have been using LVM end now LVM2 since fedora 16 without any real issues. However I am now experiencing some problems due to inconsistencies.

The volume groups are called fedora-home and fedora-root, the system-config-lvm utility returns an empty screen image description

and lvm command line tools such as lvdisplay, vgdisplay, ... all return parsing errors or cannot be found.

[root@127 mapper]# lvdisplay Parse error at byte 1599 (line 100): unexpected token Error parsing metadata for VG fedora. Cannot process volume group fedora Internal error: Volume Group fedora was not unlocked

[root@127 mapper]# lvdisplay fedora-root Volume group "fedora-root" not found Cannot process volume group fedora-root

When I run the mount command I see the LVMs mounts as /dev/mapper/fedora-root to / and / dev/mapper/fedora-home to /home correctly.
image description

The utility "disks" is the only utility to successfully read the lvm definition for the hardware partition mapped to 2 LVMs /dev/fedora/root and /dev/fedora/home. These obviously do not seem to match to the /dev/mapper/fedora-home and /dev/mapper/fedora-root. image description

Please help me make sense of these errors and ensure my configuration is without errors as I feel I am in dangerous waters as things stand. Thanks & reagrds, Patrick.

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2016-07-31 09:13:46 -0500

pja
96 ●2 ●5 ●11

Hi, I have since migrated to Fedora 24 and surprises of surprises the error displayed in my old LVM configuration has disappeared. The VG groups are readable and functional. Note also the new utility blivet-gui targeted to replace gparted (it was unable to solve the issue in Fedora 23, but is now working without a problem in Fedora 24). I am a happy user and more confident of the system enhancements / corrections brought by new versions.
Thanks, Patrick.

edit flag offensive delete link

add a comment

answered 2016-03-16 00:15:38 -0500

cmurf
1167 ●40 ●29

I'm pretty sure system-config-lvm is deprecated. What do you get for the commands

# pvs
# vgs
# lvs

Another possibility is using blivet-gui which is a newer tool that supports LVM and Btrfs.

edit flag offensive delete link

Comments

Hi, Thanks for the info cmurf, however I get same parsing error for all 3 commands. See output below (all commands return the same error)

root@127 ~]# pvs

Parse error at byte 1599 (line 100): unexpected token Error parsing metadata for VG fedora. Cannot process volume group fedora Internal error: Volume Group fedora was not unlocked

Regards, Patrick.

pja ( 2016-03-17 14:39:56 -0500 )edit

Try 'pvck' and then 'vgck' and see if anything gets fixed up.

cmurf ( 2016-03-24 13:29:47 -0500 )edit

Hi cmurf, thenks for the heads up. No luck on pvck (without options) or vgck (also without options). Feedback is still error.

Parse error at byte 1599 (line 100): unexpected token Error parsing metadata for VG fedora. Cannot process volume group fedora Internal error: Volume Group fedora was not unlocked Device '/dev/sda2' has been left open (0 remaining references). Internal error: 1 device(s) were left open and have been closed. Regards, Patrick.

pja ( 2016-05-16 02:32:06 -0500 )edit

Hi again, Looking into the system I see what seems to be the original configurtion for the LVMs in /etc/lvm/archive (file fedora_00000-1964339232.vg) and /etc/lvm/backup (file fedora). Would these help? They were generated by LVM2 version 2.02.98(2) (2012-10-15): Wed Mar 27 12:40:03 2013, "after executing 'vgchange -a ay --sysinit". They refer to the VGs I have installed with correct (same) sizes and locations (swap, root and home). How may I check the UUIDs they are referring to are the sames ones as the ones being used currently (I only see the mappings in /etc/fstab)? Tks. Patrick.

pja ( 2016-05-16 03:18:31 -0500 )edit

add a comment

Inconsistent LVM / LVM2 data

2 Answers

Comments

Question Tools

Stats

Related questions

Inconsistent LVM / LVM2 data edit

2 Answers

Comments

Question Tools

Stats

Related questions

Inconsistent LVM / LVM2 data