Veritas Storage Foundation Release Notes

62
Storage Foundation Release Notes
Known issues
A snapshot volume created on the Secondary, containing a
VxFS file system may not mount in read-write mode and
performing a read-write mount of the VxFS file systems on the
new Primary after a global clustering site failover may fail
(1558257)
Issue 1:
When the vradmin ibc command is used to take a snapshot of a replicated data
volume containing a VxFS file system on the Secondary, mounting the snapshot
volume in read-write mode may fail with the following error:
UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg/snapshot_volume
is corrupted. needs checking
This happens because the file system may not be quiesced before running the
vradmin ibc command and therefore, the snapshot volume containing the file
system may not be fully consistent.
Issue 2:
After a global clustering site failover, mounting a replicated data volume
containing a VxFS file system on the new Primary site in read-write mode may
fail with the following error:
UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg/data_volume
is corrupted. needs checking
This usually happens because the file system was not quiesced on the original
Primary site prior to the global clustering site failover and therefore, the file
systems on the new Primary site may not be fully consistent.
Workaround: The following workarounds resolve these issues.
For issue 1, run the fsck command on the snapshot volume on the Secondary, to
restore the consistency of the file system residing on the snapshot.
For example:
# fsck -F vxfs /dev/vx/dsk/dg/snapshot_volume
For issue 2, run the fsck command on the replicated data volumes on the new
Primary site, to restore the consistency of the file system residing on the data
volume.
For example:
# fsck -F vxfs /dev/vx/dsk/dg/data_volume