mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-30 17:18:21 +03:00
d97f1c89de
If we know that the PV is orphan, meaning there's at least one MDA on that PV which does not reference any VG and at the same time there's PV_EXT_USED flag set, we're certainly in an inconsistent state and we need to fix this. For example, such situation can happen during vgremove/vgreduce if we removed/reduced the VG, but we haven't written PV headers yet because vgremove stopped abruptly for whatever reason just before writing new PV headers with updated state, including PV extension flags (and so the PV_EXT_USED flag). However, in case the PV has no MDAs at all, we can't double-check whether the PV_EXT_USED is correct or not - if that PV is marked as used, it's either: - really used (but other disks with MDAs are missing) - or the error state as described above is hit User needs to overwrite the PV header directly if it's really clear the PV having no MDAs does not belong to any VG and at the same time it's still marked as being in use (pvcreate -ff <dev_name> will fix this). For example - /dev/sda here has 1 MDA, orphan and is incorrectly marked with PV_EXT_USED flag: $ pvs --binary -o+pv_in_use WARNING: Found inconsistent standalone Physical Volumes. WARNING: Repairing flag incorrectly marking Physical Volume /dev/sda as used. PV VG Fmt Attr PSize PFree InUse /dev/sda lvm2 --- 128.00m 128.00m 0 |
||
|---|---|---|
| .. | ||
| cache_manip.c | ||
| lv_alloc.h | ||
| lv_manip.c | ||
| lv.c | ||
| lv.h | ||
| merge.c | ||
| metadata-exported.h | ||
| metadata.c | ||
| metadata.h | ||
| mirror.c | ||
| pool_manip.c | ||
| pv_alloc.h | ||
| pv_manip.c | ||
| pv_map.c | ||
| pv_map.h | ||
| pv.c | ||
| pv.h | ||
| raid_manip.c | ||
| replicator_manip.c | ||
| segtype.c | ||
| segtype.h | ||
| snapshot_manip.c | ||
| thin_manip.c | ||
| vg.c | ||
| vg.h | ||