On 08/13/2018 06:48 AM, 'awokd' via qubes-users wrote:
On Mon, August 13, 2018 7:59 am, [email protected] wrote:
Should I mount each LV
and attempt to import the root.img and private.img files? How would I
mount those to get to the files, and how would import to Qubes?
Sounds pretty FUBARd. LVs don't have .img files; if you can manage to get
them mounted you might be able to recover contents. Boot from some
recovery distribution and get the Qubes PV attached, then "mount <subdir>
/dev/mapper/qubes_dom0-vm--vmname--private" for example.
Thin LVs can be imaged like normal volumes, however. I would try
'vgchange -ay' then 'lvchange -ay' on the drive and then look for the
vm*private volumes in /dev/mapper.
Once you got that, you can do stuff like this to backup:
# dd if=/dev/mapper/qubes_dom0-vm--work--private | gzip >work_img.gz
and this to restore:
# gunzip -c work_img.gz | dd
of=/dev/mapper/qubes_dom0-vm--work--private conv=sparse
This example is unencrypted, so take care with the remaining backup details.
Also keep in mind that thin-provisioned lvm is still pretty young -- it
is NOT 'like' regular non-thin lvm, but more like a new filesystem on
top of regular lvm. If reliability is high on your list then Btrfs may
be better... it seems to be older with a lot more people using it, and
has more internal error-correction mechanisms (but it still isn't
recommended for RAID5/6). Btrfs is worth considering as an alternative.
--
Chris Laprise, [email protected]
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/69368c6b-9bc6-1690-5c5b-e47c02f45b8d%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
