LVM problem

Dan Coutu coutu at snowy-owl.com
Tue Dec 18 11:48:01 EST 2007


Ben Scott wrote:
>   Which all seem to indicate that the volume group named "VolGroup00"
> is not working.
>
>   You did say this system was running, right?
>   
Right. I'm certain that it will not reboot in the current state.
>> You will note that nowhere in there is any mention of the problematic
>> uuid. Also there is no mention of the physical volume sdb, only of sda2.
>>     
>
>   That may or may not be a good thing.  It all hinges on whether any
> extents from the PV that was on sdb got allocated to any LVs at some
> point.
>   
Unlikely. I never did the lvextend command.
>   If the LVs have extents mapped to the damaged PV on sdb, then
> restoring the metadata of the damaged PV is what you want.
>
>   Try the "--partial" switch to the various LVM commands.  According
> to the man page, it will not allow modification of metadata, so it
> should be safe.  There are also some words in there about re-creating
> a missing PV and restoring LVM config that you may want to read
Interesting results:

# vgdisplay --partial
  Partial mode. Incomplete volume groups will be activated read-only.
  Couldn't find device with uuid 'oACqnk-YQTQ-IiGy-F6Pj-UoBB-kUqM-g6Yu3D'.
  Couldn't find device with uuid 'oACqnk-YQTQ-IiGy-F6Pj-UoBB-kUqM-g6Yu3D'.
  --- Volume group ---
  VG Name               VolGroup00
  System ID            
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  4
  VG Access             read
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               273.34 GB
  PE Size               32.00 MB
  Total PE              8747
  Alloc PE / Size       4369 / 136.53 GB
  Free  PE / Size       4378 / 136.81 GB
  VG UUID               AuDV2N-7nfH-7OpL-KjCN-LWVD-ArpI-7AkTBy
  
# lvdisplay --partial
  Partial mode. Incomplete volume groups will be activated read-only.
  Couldn't find device with uuid 'oACqnk-YQTQ-IiGy-F6Pj-UoBB-kUqM-g6Yu3D'.
  Couldn't find device with uuid 'oACqnk-YQTQ-IiGy-F6Pj-UoBB-kUqM-g6Yu3D'.
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol00
  VG Name                VolGroup00
  LV UUID                0ChzON-UBNj-xEdx-jrir-f5T1-nDKq-Wx4WUP
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                134.59 GB
  Current LE             4307
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0
  
  --- Logical volume ---
  LV Name                /dev/VolGroup00/LogVol01
  VG Name                VolGroup00
  LV UUID                bI5vdI-uYbl-1ME1-8LvS-VLJ8-SOyn-0tgxVZ
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.94 GB
  Current LE             62
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:1
  
So the running system is seeing the key things.

Dan


More information about the gnhlug-discuss mailing list