Kernel_init_dgdisklock: pid is 0 error

Linux and Unix-Like Red Hat
1

Hi,

In RHEL 7.7 O.S, I am getting below error while running veritas vxconfigd -f (starting vxvm daemon process. I have attached Managed disks (block disk) in azure VM.

I have a Azure VM which is a RHEL 7.7 based Linux O.S. I am trying to start veritas vxconfigd (vxvm process), its trying to claim the attached Disks but this command is getting stuck completely and system need to reboot multiple times to access vm.

vxconfigd -f (After running this command to start vxvm service getting below error). Probably kernel is locking, not exactly sure.

[root@vcs2 ~]# vxconfigd -f
VxVM vxconfigd ERROR V-5-1-18790 kernel_init_dgdisklock: pid is 0 ...gpd_claim_device: failed to claim device
gpd_claim_device: failed to claim device

Please let me know the solution.

Thanks,

2

I have never met this problem.
Perhaps an incompatibiliy between vxconfigd and the running kernel.?
Did it work before? Did it stop working since a certain kernel update? Then consider reverting to the older kernel.
Since Veritas is commercial you should try to reach their support.

3

try searching online for vxconfigd ERROR V-5-1-18790 - seems to be plenty of discussion/advice/guidance available.

4

My Google search only finds hits for similar non- 18790 errors.