Veritas Volume Manager 5.0 Release Notes HP-UX 11i v3 (5992-1952, August 2011)

When taking a snapshot of an SFCFS file system, you must ensure that at least one of the
volumes defined in the command line is mounted on the CVM master node.
• Problem
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.
Workaround
Do not perform these operations on a mounted volume.
Miscellaneous Issues
The following issues are known:
• Problem
Site failure in an Extended Distance Cluster (EDC) setup with CVM causes application I/Os
and VxVM commands to hang.
When there is a site failure in an Extended Distance Cluster (EDC) setup with CVM
configuration, the link that connects the storage devices (either A/P or A/AA array) between
the two sites is disconnected. On the remaining site, DMP does not return the I/O on the failed
paths to the application and causes application I/Os and VxVM commands to hang.
Workaround
No workaround exists for this issue.
• Problem
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.
Workaround
If it is important that a disk group not be auto-imported when the system is rebooted, the disk
group must be imported temporarily when the intention is to deport the disk group (For example,
in HA configurations). Use the -t flag with the vxdg import command.
• Problem
The vxrecover command starts a volume only if it has at least one plex that is in the ACTIVE
or CLEAN state and is not marked STALE, IOFAIL, REMOVED, or NODAREC. If such a plex
is not found, VxVM assumes that the volume no longer contains valid up-to-date data. As a
result, the volume is not started automatically. A plex can be marked STALE or as IOFAIL
as a result of a disk failure or an I/O failure.
Workaround
In such cases, to force the volume to start, use the following command:
# vxvol -f start volume
However, determine the cause of the problem before you run this command. It is likely that
the volume needs to be restored from backup, or the disk needs to be replaced.
• 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 problem occurs 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
Known Problems And Workarounds 33