Previous lock files prevent cause vxconfigbackup to hang while backing up specific disk groups and requires manual intervention to terminate process
Article ID: 100029975
Updated On:
Description
Error Message
There is no error message. The vxconfigbackup will simply hang without any output
Cause
Volume Manager includes a series of scripts to manage the creation of disk group recovery information. The /etc/vx/bin/vxconfigbackup script will create disk group back information in the /etc/vx/cbr/bk directory.
If any previous lock files or PID files are present in the /etc/vx/cbr directory a loop condition can occur in the script while it attempts to establish a fresh lock file for the disk group.
Solution
When diagnosing a vxconfigbackup hang or stall condition, examine the output of the following command:
# ls -l /etc/vx/cbr
total 2
drwxr-xr-x 4 root root 512 Dec 5 05:55 bk/
The bk/ directory entry should be the only file in that directory unless a vxconfigbackup process is running. If any PID or lock files are found, these should be removed. These files will appear with the format:
Following removal of these files the vxconfigbackup command should be completed without problems.
Resolution
When diagnosing a vxconfigbackup hang or stall condition, examine the output of the following command:
# ls -l /etc/vx/cbr
total 2
drwxr-xr-x 4 root root 512 Dec 5 05:55 bk/
The bk/ directory entry should be the only file in that directory unless a vxconfigbackup process is running. If any PID or lock files are found, these should be removed. These files will appear with the format:
Following removal of these files the vxconfigbackup command should be completed without problems.
Issue/Introduction
