During operations like vxddladm assign names, or vxddladm set namingscheme=osn, a reassignment, or change, in the name of Volume Manager (VxVM) device name ("DA record") can occur. Consequently, the device attribute list, or the in-core DMP, database should be updated for all devices to correctly map the new device name with the appropriate device number.
A problem was identified in the associated routines which caused an incorrect mapping to occur. This led to I/O being routed to the wrong device, leading to corruption.
The DMP routines responsible for the mapping of device names to numbers have been fixed in 5.1 SP1 RP2 P2 HF7, and above. Veritas has also released the 'P' patch (5.1 SP1 RP2 P3) which includes the fix for this issue. This patch, and superseded patches, are available from SORT: https://docs.infoscale.com
Avoid running vxddladm <-c> assign names on versions earlier than 5.1 SP1 RP2 P2 HF7, where third-party drivers are present.
Notes:
Applies to:
Solaris 5.1 SP1 RP1, and above, in environments that include third-party multipathing drivers, such as MPxIO, or Powerpath
Corruption can occur in Volume Manager (VxVM) configurations involving third-party multipathing drivers, like MPxIO, or Powerpath, upon executing commands like vxddladm assign names or vxddladm set namingscheme=osn. Note: The command vxddladm assign names was executed as part of a command sequence, according to best practices adopted during LUN addition, and removal.
UMI: V-5-0-1046 ETrack: 2674465