Veritas Volume Manager 4.1 Release Notes (5900-0590, March 2010)

Data Integrity Issues
Following data integrity issues are identified:
• Disks with Write-Back Caches Exhibit Data Integrity Problems
Problem
Disk drives configured to use a write-back cache, or disk arrays configured with volatile
write-back cache, exhibit data integrity problems.
Workaround
The problems occur after power failure, SCSI bus reset, or other event in which the disk has
cached data, but has not yet written it to a non-volatile storage. Contact your disk drive or
disk array manufacturer to determine whether your system disk drives use a write-back
cache, and if the configuration can be changed to disable write-back-caching.
VEA Issues
Following VEA issues are identified:
• Restarting VEA after Obtaining New Licenses
Problem
After installing a new license (either explicitly, using vxlicinst, or implicitly, by installing
the license bundles ), you will not have access to the newly licensed features until you restart
the VEA service.
Workaround
To re-start the VEA service, complete the following:
— Stop the VEA backend service:
# /opt/VRTSob/bin/vxsvcctrl stop
— Start the VEA backend service:
# /opt/VRTSob/bin/vxsvcctrl start
• Updating Objects in Volume View
Problem
Object updates in the Volume View are incorrect.
Workaround
Close and then re-open the Volume View.
• Updating Objects in Disk/Volume Map View
Problem
Object updates in the Disk/Volume Map View are incorrect.
Workaround
Close and then re-open the Disk/Volume Map View.
• Updating Objects in Disk/Volume Map View
Problem
Object updates in the Disk/Volume Map View are incorrect.
Workaround
Close and then re-open the Disk/Volume Map View.
• Mirroring Disks
Problem
16 Veritas Volume Manager 4.1 Release Notes