Remove Cluster Lock Flags from PV

[davesec]

I would like to remove the Cluster Lock Flag from a PV in a active vg without loosing the data on it and without data backup, new creation of vg, data restore.
How could this be possible?

History:
I created a cluster and defined a
FIRST_CLUSTER_LOCK_VG /dev/vg01
FIRST_CLUSTER_LOCK_PV /dev/disk/disk71

The vg01 is a cluster vg with data on it.

Then I changed the quorum from CLUSTER_LOCK_VG to a quorum server but the Locking information still exists on the disk:
# lvm.11 -a -d /dev/rdisk/disk71 | grep -i lock
/* Alternate block pool length. */ 56
/* Alternate block pool start. */ 125829052
/* Cluster-lock flags. */ LVM_CLUSTER_LOCK_INITIALIZED
/* Cluster-lock area start. */ 125829108
/* Alternate block pool length. */ 56
/* Alternate block pool start. */ 125829052
/* Cluster-lock flags. */ LVM_CLUSTER_LOCK_INITIALIZED
/* Cluster-lock area start. */ 125829108
CLUSTER LOCK fields
lock_state LVM_DISK_CL_LOCK_FREE

Now I'd like to do a vgmodify -a -E vg01 but this does not work because vgmodify thinks the disk71 is still a cluster lock lun. That leads to the question:
How can I remove this LVM_CLUSTER_LOCK_INITIALIZED flag and the Cluster-lock area from the disk71?

Can please someone provide me this lvm hack!?

Thank you

[Bob_Vance]

This does not help your situation, but

I always create a small, separate VG with no data on it for the lock VG/disks. In fact, it is kept deactivated.

Yours is a good case (which I have never run into) for my setup.


Anyway, I assume that you removed the LOCK disk config in SG.


This would appear to be a bug (or, if "bug" is too harsh, then "an area that requires further scrutiny", or "a needed enhancement" :>), in either vgmodify (why should it care) or SG (perhaps it should clear that info when a disk is removed from the LOCK configuration), and which other people have run into.

I'm surprised HP has not fixed this.


bv

[davesec]

Thank you for your reply. All your answers are definitly true.

BUT:
I'm still hoping that someone out there has a solution to edit this mf PV Header in a way that a vgmodify command is possible and no cluster locking information is on the PV anymore.

Thanks for helping me!

[Bob_Vance]

I'm not familiar with this technical term

"mf PV Header
.
It frightens and confuses me...
;>)

[davesec]

I'm sorry about that.

[Bob_Vance]

It would be painful, and maybe dangerous, but you may be able to halt the package and change the cluster flag on the disk

halt package
vgchange -a n # redundant
vgchange -c n

.
I would hope that this would remove any cluster lock flag, but no guarantees.

Then redo the cluster flag

vgchange -c y
vgchange -a e # test it
vgchange -a n # get ready for package start
start package

but it would hopefully not have any memory of LOCK.


I may play with this.

(Emil, where are you ?)


bv

[Viktor Balogh]

yepp, at first I also thought about the cluster flag on the disks (vgchange -c). but am not sure if it is related to the locking functionality.

[davesec]

I tried this allready but with the vgchange -c n only the Configured activation Modes Flags will change and the Lock information is still there...

[Bob_Vance]

yikes!

have you called HP?

[davesec]

Not yet: Because It's a really tricky issue that I'd like to discuss with the whole HP Professional community.

I think I have a better chance to resolve this issue via the forum than the HP Support.

But I'll call HP tomorrow to get additional help from there, hopping eather that someone can help me via the forum...