Veritas Volume Manager 5.0 Release Notes (5900-0593, March 2010)

Veritas Volume Manager 5.0 Release Notes
Known Issues
Chapter 1 27
Inconsistencies can arise in point-in-time copies if any of the following snapshot
operations are performed on a volume while a file system in the volume is being mounted:
vxassist snapshot, vxplex snapshot, vxsnap make, vxsnap refresh, or vxsnap
restore.
• Cache volumes in volume sets
Do not add cache volumes (used by space-optimized instant snapshots) to volume sets.
This causes data corruption and system panics. [614061, 614787]
Intelligent Storage Provisioning (ISP) Issues
NOTE The ISP feature is not available with the current release of VxVM.
• Creating application volumes
To create application volumes successfully, the appropriate licenses must be present on
your system. For example, you need a full Veritas Volume Manager and a Veritas
FlashSnap license to use the instant snapshot feature. Vendors of disk arrays may also
provide capabilities that require special licenses for certain features of their hardware.
[i137185]
Miscellaneous Issues
• Disks with write-back caches
Disk drives configured to use a write-back cache, or disk arrays configured with volatile
write-back cache, exhibit data integrity problems. The problems occur after a power
failure, SCSI bus reset, or other event in which the disk has cached data, but has not yet
written it to 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-backcaching.
• Auto-import of disk groups
If a disk that failed while a disk group was imported returns to life after the group has
been deported, the disk group is auto-imported the next time the system boots. This
contradicts the normal rule that only disk groups that are (non-temporarily) imported at
the time of a crash are auto-imported.
If it is important that a disk group not be auto-imported when the system is rebooted, the
disk group should be imported temporarily when the intention is to deport the disk group
(for example, in HA configurations). Use the -t flag to vxdg import. [i13741]