after installing Patches 1109: On disk LVM metadata structures are corrupted.

[vandevoort]

We update a number of systems Vpars and single Blade HP-UX systems .

From patch kit sept 2009 to sept 2011.

It seems in the past  in 2009  upgraded  a lot of volume groups from Version 1.0 to 2.1  (dynamic extend of a lun possible with this newer Version).

This seems to works fine for the past 2 ½ Year. periodical a vgcfgbackup was made of all Volume groups .

But now during Installing the patch bundle (sept 2011)after first reboot  we encountered this problem ..for  some  volumegroups which were updated in the past , not all Volume-groups ..

vgchange -a y vg05PS1d1                                  
vgchange: Couldn't activate volume group "vg05PS1d1":
On disk LVM metadata structures are corrupted.

I found in the Release Guide ,

 After the migration of a volume group from version 1.0 to 2.x using vgversion, the volume

group activation fails with the following error message:

$vgchange –a y vgname

Coundn't activate volume group vgname

On disk, LVM metadata structure are corrupt.

Resolution notes: vgversion has been enhanced so that volume groups migrated using the

March 2012 version of vgversion will successfully activate. Volume groups migrated using

older unfixed versions of vgversion may continue to face this problem. See notes against

QXCR1001182973 under “Known issues” (page 6) for more details.

Defect ID: QXCR1001182973

2.x VG fails to activate with “On disk LVM metatdata structures are corrupted” error message

Problem: Volume groups that were migrated from 1.0 to 2.X using a version

of vgversion prior to the August 2011 web release or using the

September 2011 release may fail to activate, resulting with the error

message: “On disk LVM metadata structures are

corrupted”.

Corrective Action: To fix this problem, restore the volume group back to its 1.0 version

configuration using the vgcfgrestore command, and then migrate

to 2.x using the new enhanced vgversion command, first made

available in the August 2011 web release (after September 2011

release) and also provided in the March 2012 release.

This could be the issue .

the  odd  thing in this is that we do have this on only a few volume groups  ( from resent about  10 systems updates , with each about 10 or  more  volume groups  only had  3  Volume groups  with this  problem ).

while  on regular base  a vgcfgbackup is  made , we do  not have a config for  these volume groups   while they were V1.0 anymore , overwritten by vfgcfgbackup.

Our question / request  :  is  there a way  we can easily Check  ( before we start the  update ) which volume group  could have this  issue  ?

[Per Christensen_1]

Hi There

Don't know how you can check for this issue before convertion.

BUT, do you have directories named vgversion_*  in /etc/lvmconf ?

These should contain conf files and restore script to go back to v 1

Just a thought,

[vandevoort · Accepted solution]

---

@Per Christensen_1 wrote:

Hi There

Don't know how you can check for this issue before convertion.

BUT, do you have directories named vgversion_*  in /etc/lvmconf ?

These should contain conf files and restore script to go back to v 1

Just a thought,

---

Thanks  .

yes I know  , but the  update V1.0 to V2.1  is  done  on most Volumegroups  in 2009  and 2010 , since then a lot of Volumegroups  are  extended , so the  /etc/lvmconf/vgversion_vg132appl/vg132appl_1.0.conf will probably not valid  to use anymore  ....

any other idea's  except  terrabytes  of recovery  on dozens of systems    :=( ..

kind regards  Wim .