[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] F7 will not boot after running backup w/snapshot



Hello,

Friday, May 2, 2008, 16:47:58, Bryn M. Reeves wrote:

> - -P | --partial
>  When set, the tools will do their best to provide access to volume
>  groups that are only partially available.  Where part of a logical
>  volume is missing, /dev/ioerror  will be substituted, and you could use
>  dmsetup (8) to set this up to return I/O errors when accessed, or
>  create it as a large block device of nulls.  Metadata may not be
>  changed with this option. To insert a replacement physical volume of
>  the same or large size use pvcreate -u to set the uuid to match the
>  original followed by vgcfgrestore (8).

> You can also choose the device used for mapping segments on any
> incomplete logical volumes by setting the missing_stripe_filler
> parameter in the activation section of lvm.conf.

It is not the same. I was doing this about 2 years ago when one HDD
died and I wanted to recover as much data as possible (I mean data
changes since last backup), but it was not possible to activate the VG
with missing PV (or activate only read-only, which prevented me from
mounting the filesystem, because it required fsck, which cannot be
done on readonly lvol). I had to google quite a lot on how to create
this "virtual" PV with dmsetup which returned all zeros (or I/O
errors). It had to be the same size as original (but fortunately you
can create 100 GB sparse file in RAM and use loop to turn it into
PV)... But this is only for recovery - you are making "virtual"
identical PV instead of the original missing... So it is definitely
not the same as activating VG/LV with missing PV.


-- 
  bYE, Marki


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]