LVM Error

I was recently going to reboot my machine to add some hardware, I had not yet done anything to the LVM nor rebooted the machine and got the following when looking at my lvm.

http://ultimate.kicks-ass.net/files/lvm.txt

Can anyone suggest what I might need to do in order to get me back up and running?

Terry

I might also add that I get this problem every single time I want to reboot my machine. Which leads me to believe that maybe I have setup my LVM wrong or something.

FYI I am running debian sarge on this box.

Terry Rigby

  PV /dev/hda2        VG 4474   lvm2 [18.18 GB / 0    free]
  PV /dev/hdc         VG 4474   lvm2 [74.53 GB / 0    free]
  PV /dev/hdb         VG 4474   lvm2 [74.53 GB / 0    free]
  PV unknown device   VG 4474   lvm2 [74.53 GB / 0    free]

Which version of LVM2?
Try upgrading it to at least 2.00.33.

Does hdd have a partition table on it (even an empty one)? Is the PV meant to be hdd or hdd1?
If the PV is genuinely hdd not hdd1 and there's a partition table, try removing it.

Alasdair

[email protected]

I am using lvm2.
PV is /dev/hdd
no partition table exists.

I did figure out the problem though. I had a symlink to /dev/hdd and I think that was causing some issues. I removed that symlink and all the PV's display properly now. My next issue is this..

fileserver:~# vgchange -a y 4474
  Volume group 4474 metadata is inconsistent
  Volume group for uuid not found: 
lIoGSWjLzjHDN61mdY0yqVbilyBU9xzFSoVzKiy750swPFxT8D0ijXGNAi3FddlG
  0 logical volume(s) in volume group "4474" now active

:(
hehe, next...

Terry Rigby

Ah. Debian cdrom mix-up again?

Need more info: why it's inconsistent. [Add -vvvv with 2.00.33]

Compare the metadata on each disk [vgcfbackup -P -f file] and see if one of them is different/wrong. If so, vgcfgrestore from the correct version.

Alasdair

[email protected]

This is from "vgcfgbackup -P -f file.txt"

fileserver:~# cat file.txt |grep "id ="
VG (4474)      id = "lIoGSW-jLzj-HDN6-1mdY-0yqV-bily-BU9xzF"
pv0 (hda2)     id = "hxeJjE-AgPR-letG-U0rH-FlDP-hOu9-o7UH7e"
pv1 (hdc)       id = "KMzdEO-aigL-KoHL-2ZED-SgWf-CsoW-7qEWQP"
pv2 (hdb)       id = "2MKTrn-jv8Y-hUPU-8W6m-Uur1-ItpE-Abq3w4"
pv3  (hdd)      id = "ISBKAD-7SQt-B9Bo-ppng-G5Q6-Iu3D-uABjz7"
LV  (storage) id = "SoVzKi-y750-swPF-xT8D-0ijX-GNAi-3FddlG"

and

fileserver:~# vgdisplay -v |grep "UUID"
  VG UUID               lIoGSW-jLzj-HDN6-1mdY-0yqV-bily-BU9xzF
  LV UUID                SoVzKi-y750-swPF-xT8D-0ijX-GNAi-3FddlG
  PV UUID               hxeJjE-AgPR-letG-U0rH-FlDP-hOu9-o7UH7e <-- hda2
  PV UUID               KMzdEO-aigL-KoHL-2ZED-SgWf-CsoW-7qEWQP <-- hdc
  PV UUID               2MKTrn-jv8Y-hUPU-8W6m-Uur1-ItpE-Abq3w4 <-- hdb
  PV UUID               ISBKAD-7SQt-B9Bo-ppng-G5Q6-Iu3D-uABjz7 <-- hdd

vgchange -a y 4474 -vvvv can be see@
http://ultimate.kicks-ass.net/files/lvm2.txt

I dont see any differences there. Any other advice?

Terry Rigby

one more thing I just noticed...

fileserver:~# vgscan -vv
      Setting global/locking_type to 1
      Setting global/locking_dir to /var/lock/lvm
      File-based locking enabled.
    Wiping cache of LVM-capable devices
      /dev/4474.old/storage: stat failed: No such file or directory
      /dev/cdrom: stat failed: No such file or directory
    Wiping internal cache
  Reading all physical volumes.  This may take a while...
    Finding all volume groups
      /dev/hda: No label detected
      /dev/hdc: lvm2 label detected
      /dev/hdc1: No label detected
      /dev/hda2: lvm2 label detected
      /dev/hda5: No label detected
      /dev/hda6: No label detected
      /dev/hda7: No label detected
      /dev/hdb: lvm2 label detected
      /dev/hdd: lvm2 label detected
      /dev/hdb1: No label detected
      Locking /var/lock/lvm/V_4474 RB
    Finding volume group "4474"
      /dev/hda2: lvm2 label detected
      /dev/hdc: lvm2 label detected
      /dev/hdb: lvm2 label detected
      /dev/hdd: lvm2 label detected
      /dev/hda2: lvm2 label detected
      /dev/hdc: lvm2 label detected
      /dev/hdb: lvm2 label detected
      /dev/hdd: lvm2 label detected
      /dev/hda2: lvm2 label detected
      /dev/hdc: lvm2 label detected
      /dev/hdb: lvm2 label detected
      /dev/hdd: lvm2 label detected
  Found volume group "4474" using metadata type lvm2
      Unlocking /var/lock/lvm/V_4474

the two lines " /dev/4474.old/storage: stat failed: No such file or
directory" and " /dev/cdrom: stat failed: No such file or directory"
I find curious. This could be nothing but then again, maybe it is. I am really too new to LVM to know.

Terry Rigby

nevermind, I am an idiot. those are just dead symlinks.

My problem does still persist though.

fileserver:~# vgscan -vv
      Setting global/locking_type to 1
      Setting global/locking_dir to /var/lock/lvm
      File-based locking enabled.
     Wiping cache of LVM-capable devices
      /dev/4474.old/storage: stat failed: No such file or directory
      /dev/cdrom: stat failed: No such file or directory
     Wiping internal cache
   Reading all physical volumes.  This may take a while...
     Finding all volume groups
       /dev/hda: No label detected
       /dev/hdc: lvm2 label detected
       /dev/hdc1: No label detected
       /dev/hda2: lvm2 label detected
       /dev/hda5: No label detected
       /dev/hda6: No label detected
       /dev/hda7: No label detected
       /dev/hdb: lvm2 label detected
       /dev/hdd: lvm2 label detected
       /dev/hdb1: No label detected
       Locking /var/lock/lvm/V_4474 RB
     Finding volume group "4474"
       /dev/hda2: lvm2 label detected
       /dev/hdc: lvm2 label detected
       /dev/hdb: lvm2 label detected
       /dev/hdd: lvm2 label detected
       /dev/hda2: lvm2 label detected
       /dev/hdc: lvm2 label detected
       /dev/hdb: lvm2 label detected
       /dev/hdd: lvm2 label detected
       /dev/hda2: lvm2 label detected
       /dev/hdc: lvm2 label detected
       /dev/hdb: lvm2 label detected
       /dev/hdd: lvm2 label detected
   Found volume group "4474" using metadata type lvm2
       Unlocking /var/lock/lvm/V_4474

the two lines " /dev/4474.old/storage: stat failed: No such file or
directory" and " /dev/cdrom: stat failed: No such file or directory"
I find curious. This could be nothing but then again, maybe it is. I am really too new to LVM to know.

Terry Rigby