summaryrefslogtreecommitdiffstats
path: root/man/dmsetup.8.in
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2012-07-26 17:06:06 -0500
committerJonathan Brassow <jbrassow@redhat.com>2012-07-26 17:06:06 -0500
commit186a2772e8ac3c2088bdfc833c32d773464d666b (patch)
tree3650045026ecb902565a64133a13976afec8e476 /man/dmsetup.8.in
parent45db25817ff342a86b2ddf000b4b3a4d59be8848 (diff)
downloadlvm2-186a2772e8ac3c2088bdfc833c32d773464d666b.tar.gz
lvm2-186a2772e8ac3c2088bdfc833c32d773464d666b.tar.xz
lvm2-186a2772e8ac3c2088bdfc833c32d773464d666b.zip
vgextend: Allow PVs to be added to VGs that have PVs missing
Allowing people to add devices to a VG that has PVs missing helps people avoid the inability to repair RAID LVs in certain cases. For example, if a user creates a RAID 4/5/6 LV using all of the available devices in a VG, there will be no spare devices to repair the LV with if a device should fail. Further, because the VG is missing a device, new devices cannot be added to allow the repair. If 'vgreduce --removemissing' were attempted, the "MISSING" PV could not be removed without also destroying the RAID LV. Allowing vgextend to operate solves the circular dependency. When the PV is added by a vgextend operation, the sequence number is incremented and the 'MISSING' flag is put on the PVs which are missing.
Diffstat (limited to 'man/dmsetup.8.in')
0 files changed, 0 insertions, 0 deletions