#279 Issue `closed`: LVM¶

Labels: support / question

smmwizard opened issue at 2013-07-15 05:45:¶

Dears

I have a virtual machine with 2 volume group in LVM as below:

# lvscan
  ACTIVE            '/dev/VGdisks/lvroot' [216.00 MB] inherit
  ACTIVE            '/dev/VGdisks/lvtmp1' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvtmp2' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvtmp3' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvtmp4' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvtmp5' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvlog' [1.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvphys' [2.00 GB] inherit
  ACTIVE            '/dev/VGdisks/lvbsi' [10.00 GB] inherit
  ACTIVE            '/dev/VolGroup00/LogVol00' [10.03 GB] inherit
  ACTIVE            '/dev/VolGroup00/LogVol01' [9.84 GB] inherit

The machine has 2 disk ( 20GB for VolGroup00 and 30GB for VGdisks).
VolGroup00 used for / and its filesystems.
VGdisks used for raw disk in informix in this machine.

But when I create backup with rear and recover it in new VM, the rear only can create 1 VG (VolGroup00) and it didn't create VGdisks and its logical volumes.

Do you have any ideas?

Thanks

gdha commented at 2013-07-29 18:04:¶

Have a look at cat /var/lib/rear/layout/disklayout.conf
If VGdisks contains SAN disks then it is a standard behaviour.

smmwizard commented at 2013-07-31 10:11:¶

Hi
As you can see in below lines, rear comment all command related to VGdisks. it is physical disk and we created raw disk on it and we are using in informix:

# cat disklayout.conf
#disk /dev/hdc 4294965248
disk /dev/sda 21474836480 msdos
part /dev/sda 106896384 32256 primary boot /dev/sda1
part /dev/sda 21361052160 106928640 primary lvm /dev/sda2
#disk /dev/sdb 32212254720
#lvmdev /dev/VGdisks /dev/sdb P0GDIL-sAfL-CfXm-dzhI-lG1V-IAwu-ftQ8EE 62914560
lvmdev /dev/VolGroup00 /dev/sda2 5XBlKQ-iEig-cJwW-QSlr-UVOY-dAB5-J3dt3R 41720805
#lvmgrp /dev/VGdisks 4096 7679 31453184
lvmgrp /dev/VolGroup00 32768 636 20840448
#lvmvol /dev/VGdisks lvroot 54 442368
#lvmvol /dev/VGdisks lvtmp1 512 4194304
#lvmvol /dev/VGdisks lvtmp2 512 4194304
#lvmvol /dev/VGdisks lvtmp3 512 4194304
#lvmvol /dev/VGdisks lvtmp4 512 4194304
#lvmvol /dev/VGdisks lvtmp5 512 4194304
#lvmvol /dev/VGdisks lvlog 256 2097152
#lvmvol /dev/VGdisks lvphys 512 4194304
#lvmvol /dev/VGdisks lvbsi 2560 20971520
lvmvol /dev/VolGroup00 LogVol00 321 21037056
lvmvol /dev/VolGroup00 LogVol01 315 20643840
fs /dev/mapper/VolGroup00-LogVol00 / ext3 uuid=68a9d908-7d6a-4140-9bcf-86cd00ea47a4 label= blocksize=4096 reserved_blocks=4% max_mounts=-1 check_interval=0d bytes_per_inode=4094 options=rw,usrquota
fs /dev/sda1 /boot ext3 uuid=7602ba04-3d97-48a1-b2a5-a13f3bc0f126 label=/boot blocksize=1024 reserved_blocks=4% max_mounts=-1 check_interval=0d bytes_per_inode=4094 options=rw
swap /dev/mapper/VolGroup00-LogVol01 uuid= label=

gdha commented at 2013-08-02 07:58:¶

@jhoekx Jeroen, what does the savelayout code do with raw devices? Hope you can tell us without digging into the source code... thx

gdha commented at 2013-10-02 11:48:¶

@smmwizard is it possible to attach the output of rear -vD savelayout as a gist?

gdha commented at 2013-11-04 15:53:¶

@smmwizard rear only does mounted VG/FS by default. However, if you uncoment all VGdisks related lines in the disklayout.conf file they will be recreated - not populated (I repeat VGdisks lvols will be empty as you must use an external backup program to restore these).
Guess this answers your question - can we close this issue?

[Export of Github issue for rear/rear.]

#279 Issue closed: LVM¶