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

Bryn M. Reeves bmr at redhat.com
Fri May 2 14:47:58 UTC 2008

Hash: SHA1

Stuart D. Gathman wrote:
> When activating a VG, missing PVs should be marked "missing", and show as 
> such with pvs.  Missing PVs should behave exactly as if they were
> not missing, but have I/O errors on every operation.  Every attempted
> I/O on a missing PV should cause a synthetic "missing PV" error.  This
> should make mirrors, etc, do the right thing.  LVs partially on the
> missing PV could be mountable, getting errors for spots on the missing PV.
> The could be an option on vgchange for --ignoremissingpv to activate
> with missing PVs.  You might not want to activate with a root filesystem
> partially on a missing PV (filesystem corruption).  

Am I missing something here? vgchange --partial seems like it will do
what you want (man 8 lvm):

- -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.


Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the linux-lvm mailing list