"VCS ERROR V-16-10001-5586 Mount point <mount_point> is busy with some other block device."
Article ID: 100026643
Updated On:
Description
Error Message
VCS ERROR V-16-10001-5586 (server) Mount:mount_mntpoint:monitor:Mount point /
Cause
The behavior has several possible causes:
1. This mount resource was conflicting with another service group that is listed in the main.cf, in the same cluster (offline and frozen) that performs a similar mount function.
2. Two different LUNs (disks) attempted to mount to the same mount point.
3. One LUN is mounted on top of another LUN, hiding its mount point. This may occur when nested mount points are not mounted in the correct order.
Example:
User wants to have nested mount points /oracle and /oracle/locks. The Unix command df shows the mount points in the order they were mounted. A correct df -h for nested mount points looks like this:
|
Filesystem size used avail capacity Mounted on |
An incorrect configuration has a df -h that looks like this:
|
Filesystem size used avail capacity Mounted on /dev/vx/dsk/datadg/locks |
In this case, /oracle is mounted on top of /oracle/locks, causing /oracle/locks to be hidden from the Mount agent. The Mount agent issues an error message to /var/VRTSvcs/log/engine_A.log:
Resolution
- Ensure that LUNs are mounted in the correct order.
- Ensure that a single mount point is not being used by multiple resources within the same cluster.
- Verify that cluster resource, and group dependencies, are correct.
Note: The cluster configuration can be reviewed from the main.cf file. Dependencies are noted by "requires" statements.
Issue/Introduction
Additional Information
