12.5. Restoring metadata on an LVM physical volume

Procédure

1. Restore the metadata on the physical volume:

   # pvcreate --uuid physical-volume-uuid \
              --restorefile /etc/lvm/archive/volume-group-name_backup-number.vg \
              block-device

   Copy to Clipboard Toggle word wrap
   Note

   The command overwrites only the LVM metadata areas and does not affect the existing data areas.

   Exemple 12.4. Restoring a physical volume on /dev/vdb1

   The following example labels the /dev/vdb1 device as a physical volume with the following properties:

   • The UUID of FmGRh3-zhok-iVI8-7qTD-S5BI-MAEN-NYM5Sk
   • The metadata information contained in VG_00050.vg, which is the most recent good archived metadata for the volume group

   # pvcreate --uuid "FmGRh3-zhok-iVI8-7qTD-S5BI-MAEN-NYM5Sk" \
              --restorefile /etc/lvm/archive/VG_00050.vg \
              /dev/vdb1
   
     ...
     Physical volume "/dev/vdb1" successfully created

   Copy to Clipboard Toggle word wrap

2. Restore the metadata of the volume group:

   # vgcfgrestore myvg
   
     Restored volume group myvg

   Copy to Clipboard Toggle word wrap

3. Display the logical volumes on the volume group:

   # lvs --all --options +devices myvg

   Copy to Clipboard Toggle word wrap

   The logical volumes are currently inactive. For example:

     LV     VG   Attr   LSize   Origin Snap%  Move Log Copy%  Devices
     mylv myvg   -wi--- 300.00G                               /dev/vdb1 (0),/dev/vdb1(0)
     mylv myvg   -wi--- 300.00G                               /dev/vdb1 (34728),/dev/vdb1(0)

   Copy to Clipboard Toggle word wrap

4. If the segment type of the logical volumes is RAID, resynchronize the logical volumes:

   # lvchange --resync myvg/mylv

   Copy to Clipboard Toggle word wrap

5. Activate the logical volumes:

   # lvchange --activate y myvg/mylv

   Copy to Clipboard Toggle word wrap
6. If the on-disk LVM metadata takes at least as much space as what overrode it, this procedure can recover the physical volume. If what overrode the metadata went past the metadata area, the data on the volume may have been affected. You might be able to use the fsck command to recover that data.