Error Code details
V-5-0-1285
Severity: Warning 
Component: Volume Manager 
Message:
voldmp_errbuf_sio_start: Failed to flush the error buffer %p on device 0x%lx to DMP
Description:

This message displays when VxVM encounters an I/O error, but the I/O buffer cannot be transferred to Dynamic Multi-Pathing (DMP) for error analysis.

 

This situation may occur when I/O is sent to a device that is single-pathed, or a device that is multi-pathed with a third-party driver (TPD), if the device is not configured in DMP.

 

Note: This message applies to VxVM 4.1 and later on all platforms.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2010-10-29 01:27:27 PDT
Platform: Solaris 8 (SPARC)
Release: 5.0MP3
Content:

Find the operating system device name (in the /dev/dsk directory on Solaris) corresponding to the device number (dev_t) printed in the UMI message. After you have the device name, check if it is configured in the DMP database. Do the following:

Find the operating system device file entry corresponding to dev_t. For example, on Solaris, enter the following command to the find the minor number (the last 32 bits) in decimal:

ls -lL /dev/dsk/* | grep "minor"

From the matching /dev/dsk/osdevice entry, specify the name of the osdevice in the following command to determine if the device is configured in DMP:

vxdmpadm getdmpnode nodename=osdevice 
  
If the device is not present in DMP, determine why DMP is not seeing it. This can be due to changes in the configuration, such as devices connected to the system, changes in the VxVMdevice exclude list, and so on.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service