Opened 11 years ago
Closed 11 years ago
#707 closed defect (worksforme)
Mondo 3.0.3-1 unable to mount non-root LVM VG/filesystem during ISO Interactive/Automatic restore
Reported by: | Mauro Gameng | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | normal | Milestone: | 3.0.5 |
Component: | mondo | Version: | 3.0.3 |
Severity: | normal | Keywords: | |
Cc: |
Description
I'm using the following:
VirtualBox : v.4.2.12 Linux : CentOS release 6.4 (Final) mondo : 3.0.3-1.rhel6.i386 mindi-busybox : 1.18.5-3.rhel6.i386 mindi : 2.1.5-1.rhel6.i386
I used mondoarchive interactive in creating and restoring the ISO image.
Attachments (2)
Change History (6)
by , 11 years ago
Attachment: | mondorestore.log added |
---|
by , 11 years ago
Attachment: | mondoarchive.log added |
---|
follow-up: 3 comment:1 by , 11 years ago
follow-up: 4 comment:2 by , 11 years ago
Hi,
I noticed that when I restore the ISO image to a NEW ROOT disk on the same server with all the data disks left intact with all their data and disk config, I get the error above. But when I restore the ISO image to the same server but with NEW set of disks, the image restore completes without any issue.
My objective in doing this image restore test is to recover just the system disk / OS of a particular server without having to restore the contents of the non-root disks.
I really appreciate any help you can provide for me to successfully accomplish my goal.
Thanks,
comment:3 by , 11 years ago
Replying to mgameng:
I found these in the the log, I just don't know how to fix them.
lvm vgchange -a y vg_centos --> 0 lvm lvcreate -L 17960m -r auto -n lv_root vg_centos --> 0 lvm lvcreate -L 336.00m -r auto -n lv_swap vg_centos --> 0 lvm lvcreate -L 10240m -r auto -n lvol0 data2 --> 1280 failed so removing lvm just in case
lvcreate -L 10240m -r auto -n lvol0 data2 --> 1280
[Main] mondo-prep.c->do_my_funky_lvm_stuff#335: echo "lvm lvcreate -L 336.00m -r auto -n lv_swap vg_centos" >> /tmp/out.sh... so I'll get creative.
lvcreate -L 335m m -r auto -n lvol0 data2 --> 1
lvm lvcreate -L 10240m -r auto -n lvol0 data1 --> 1280 failed so removing lvm just in case
lvcreate -L 10240m -r auto -n lvol0 data1 --> 1280
[Main] mondo-prep.c->do_my_funky_lvm_stuff#335: echo " lvcreate -L 335m m -r auto -n lvol0 data2" >> /tmp/out.sh... so I'll get creative.
lvcreate -L 335m m -r auto -n lvol0 data1 --> 1
lvm vgscan --> 0
In some cases it seems the value computed for LVM are just a bit too high, and the re-creation iof LVM volumes fails. You can try adapting your /tmp/i-want-my-lvm to check whether this is indeed the issue.
comment:4 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Replying to mgameng:
Hi,
I noticed that when I restore the ISO image to a NEW ROOT disk on the same server with all the data disks left intact with all their data and disk config, I get the error above. But when I restore the ISO image to the same server but with NEW set of disks, the image restore completes without any issue.
My objective in doing this image restore test is to recover just the system disk / OS of a particular server without having to restore the contents of the non-root disks.
I really appreciate any help you can provide for me to successfully accomplish my goal.
Thanks,
Have you excluded the data disks from your backup ? From you log it appears that not !! So that's the major reason of your issues. Exclude the /dev/mapper devices hosting your data PV.
I found these in the the log, I just don't know how to fix them.
lvm vgchange -a y vg_centos --> 0 lvm lvcreate -L 17960m -r auto -n lv_root vg_centos --> 0 lvm lvcreate -L 336.00m -r auto -n lv_swap vg_centos --> 0 lvm lvcreate -L 10240m -r auto -n lvol0 data2 --> 1280 failed so removing lvm just in case
lvm lvcreate -L 10240m -r auto -n lvol0 data1 --> 1280 failed so removing lvm just in case
lvm vgscan --> 0