Veritas Storage Foundation and High Availability Solutions Release Notes

118About Veritas Storage Foundation and High Availability SolutionsKnown issuesMultiple CFSmount resources are in a single service group theymay not all come online after a reboot (2164670)In some cases when multiple CFSmount resources are in a single service group,they all may not come online after a reboot. You will need to manually bring themonline after a reboot.WorkaroundCreate a resource dependency between the various CFSmount resources.NFS issues with VxFS Storage Checkpoints (2027492)NFS clients mounting VxFS Storage Checkpoints that are NFS-exported by SFHAcluster nodes using a Virtual IP may receive the following error message uponVirtual IP failover:Stale NFS file handleThis is a result of major numbers of VxFS Storage Checkpoints not necessarilybeing the same on all SFHA cluster nodes.Workaround: There is no workaround for this issue.Panic due to null pointer de-reference in vx_bmap_lookup()(3038285)A null pointer dereference in the vx_bmap_lookup() call can cause a panic.Workaround: Resize the file system with the fsadm command from the primarynode of the cluster.File system check daemon fails to restart after abnormaltermination (2720034)The file system check daemon (vxfsckd) fails to update the vxfsckd-pid file withthe new process ID (pid) of the vxfsckd process after abnormal termination. As aresult, the CFSfsckd agent fails to detect the status of the vxfsckd daemon.Workaround: Perform the following steps to resolve the issue on the node wherethe vxfsckd resource faults:1. Log into the node as the root user.2. Kill all vxfsckd processes:# kill -9 `ps -ef|grep vxfsckd|awk '{print $2}'`