vgchange: Failed to notify clvm daemon

[Ralph Grothe]

Hello,

we've got a strange problem.

We repeatedly recreated from the very beginnig LVM character device for this VG (no name clashes in minor Nos.),
forced a new LIF header on the PV by pvcreate -f, and recreated the VG (finally without any additional arguments but the PV).

No way, the VG after having been created cannot be deactivated, but the error message below appears.

I submitted this vgchange command to tusc
to maybe see what's going on, and where something is lacking.
You may find the syscall trace attached.
I only stripped of a couple hundred lines in the middle, where there are no errors,
and there are only collective read()s of the many PVs available to LVM.

I already found another thread of someone who experienced something similar.
Unfortunately the only solution presented
was to reboot the system which,
need I mention, we cannot do at the moment.

This is the failing command:


# tusc -fpT %X -o /tmp/vgchg_vg30h.trc vgchange -a n vg30h
vgchange: Failed to notify clvm daemon about volume group deactivation - No such file or d
irectory
Couldn't deactivate volume group "vg30h":
No such file or directory


Rgds.
Ralph

[Steve Steel]

Hi


Probably corruption

Recover the LVM structure data from the vgcfgbackup saved data using
vgcfgrestore -n /dev/vg## /dev/rdsk/c#t#d#.



Steve Steel

[Ralph Grothe]

Hi Steve,

please see attachment for sequence of commands I executed.

[Ralph Grothe]

Ouch, with the last vgcfgrestore I passed the block instead of the character device.

However, the disk has meanwhile been urgently claimed by our Informix DBA so that I cannot repeat the command.
I assume the disk has already been allocated to a new VG by him :-(