'Inconsistent metadata found for VG [vgname] - updating to use version [ver.no.]' and 'Missing device /dev/[device_name] reappeared, updating metadata for VG [vgname] to version [ver.no.]' errors observed
Issue
-
Errors similar to the following appear in the output of lvm commands (version numbers keep increasing with time and frequently reach hundreds or even thousands):
WARNING: Inconsistent metadata found for VG vg00 - updating to use version 33 WARNING: Volume Group vg00 is not consistent. WARNING: Inconsistent metadata found for VG vg01 - updating to use version 5162 WARNING: Volume Group vg01 is not consistent. WARNING: Inconsistent metadata found for VG vg02 - updating to use version 348 WARNING: Volume Group vg02 is not consistent.
-
In some cases, devices are marked as missing and the errors above are accompanied by:
Couldn't find device with uuid aaaaaa-aaaa-aaaa-aaaa-aaaa-aaaa-aaaaaa. Couldn't find device with uuid bbbbbb-bbbb-bbbb-bbbb-bbbb-bbbb-bbbbbb. Couldn't find device with uuid cccccc-cccc-cccc-cccc-cccc-cccc-cccccc. Couldn't find device with uuid dddddd-dddd-dddd-dddd-dddd-dddd-dddddd. Missing device /dev/mapper/mpathb reappeared, updating metadata for VG vg00 to version 1029. Device still marked missing because of allocated data on it, remove volumes and consider vgreduce --removemissing. Missing device /dev/mapper/mpathc reappeared, updating metadata for VG vg01 to version 1029. Device still marked missing because of allocated data on it, remove volumes and consider vgreduce --removemissing. Missing device /dev/mapper/mpathd reappeared, updating metadata for VG vg03 to version 1029. Device still marked missing because of allocated data on it, remove volumes and consider vgreduce --removemissing.
-
When the problem appears in parallel with a pvmove operation, pvmove may fail. If pvmove is run in the foreground (i.e. without the -b option), messages similar to the following can appear when pvmove fails, if the modification of metadata marks a PV as missing:
-
Red Hat Enterprise Linux 6:
# pvmove --atomic /dev/mapper/mpatha /dev/mapper/mpathb /dev/mapper/mpatha: Moved: 0,0% WARNING: Inconsistent metadata found for VG vg00 - updating to use version 341 Missing device /dev/mapper/mpathb reappeared, updating metadata for VG vg00 to version 341. Device still marked missing because of allocated data on it, remove volumes and consider vgreduce --removemissing. Cannot change VG testvg while PVs are missing. Consider vgreduce --removemissing. ABORTING: Can't reread VG for /dev/mapper/mpatha.
-
Red Hat Enterprise Linux 7:
# pvmove --atomic /dev/mapper/mpatha /dev/mapper/mpathb /dev/mapper/mpatha: Moved: 0,01% WARNING: Missing device /dev/mapper/mpathb reappeared, updating metadata for VG vg00 to version 523. WARNING: Device /dev/mapper/mpathb still marked missing because of allocated data on it, remove volumes and consider vgreduce --removemissing. WARNING: Inconsistent metadata found for VG vg00 - updating to use version 523 /dev/mapper/mpatha: Moved: 8,89% LVM command executed by lvmpolld failed. For more information see lvmpolld messages in syslog or lvmpolld log file.
-
Environment
- Red Hat Enterprise Linux 5
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7
- MicroFocus (or previously Hewlett-Packard Enterprise) package named HPOvPerfMI - Part of Systems Management (OpenView-OP Mgmt)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.