Veritas Volume Manager (VxVM) 5.0 MP3 (Solaris) will report "VxVM vxconfigd ERROR V-5-1-13992 open failed on path" messages for devices in a Not-Ready (NR) or corresponding state.

Problem

Veritas Volume Manager (VxVM) 5.0 MP3 (Solaris) will report "VxVM vxconfigd ERROR V-5-1-13992 open failed on path" messages for devices in a Not-Ready (NR) or corresponding state.

These messages are harmless, however, can be several lines depending on the amount of luns in such a device state.

Error Message

The following vxdg import (WARNING,NOTICE) messages are taken from the product enhancement introduced in 5.0 MP3 RP5 HF7 (Solaris) surrounding the improved visiblity error messaging during the diskgroup import process.


# vxdg -n bcv_prodg -o useclonedev=on -o updateid import prodg
VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0033 <<<<
VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0034  <<<<
VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0035 <<<<<
VxVM vxconfigd WARNING V-5-1-0 Disk Group only has cloned disks or useclonedev=on option is specified: Trying to import the disk group from the cloned disks
VxVM vxconfigd NOTICE V-5-1-0 Selecting configuration database copy from emc0_00eb from disks: emc0_00eb
VxVM vxconfigd NOTICE V-5-1-0 Trying to import the disk group using configuration database copy from emc0_00eb

Etrack 2643647 (2643650) contains the vxdg import message enhancements

Cause

In this instance, the following dmpnode names "emc0_0033, emc0_0034 and emc0_0035" refer to BCV luns in an established (Not-Ready state).

VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0033 <<<<
VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0034  <<<<
VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_0035 <<<<<


Such messages can be safely ignored in this instance.

Solution

The "VxVM vxconfigd ERROR V-5-1-13992 open failed on path" messages are masked in Veritas Volume Manager 5.1

The required code change has been done through e1252086

Etrack 1252086 Vxconfigd log enhancement for VE_VOLDERR

The risk of code regression is very high, Veritas has no plan to port the changes back to 5.0. Veritas would advise customers to upgrade to 5.1 SP1 RP2 P2 HF8 (Solaris) onwards to address this issue.

Applies To

Solaris