Veritas Storage Foundation and High Availability Solutions Release Notes

116About Veritas Storage Foundation and High Availability SolutionsKnown issuesUse the following commands for this situation:hastop -localrm /var/adm/cfs/vxfsckd-pidKill all vxfsckd processes:fsclustadm cfsdeinithastartNFS issues with VxFS checkpoint (2027492)NFS clients mounting VxFS checkpoints that are NFS-exported by SFCFS or 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 checkpoints not necessarily being thesame on all SFCFS or SFHA cluster nodes.There is no workaround at this time.The mount command may hang when there are large numberof inodes with extops and a small vxfs_ninode, or a full fsckcannot fix the link count table corruptions (2689326)You might encounter one of the following issues:■■If there are large number of inodes having extended operations (extops), thenthe number of inodes used by the mount command reaches the maximumnumber of inodes that can be created in core. As a result, the mount commandwill not get any new inodes, which causes the mount command to run slowlyand sometimes hang.Workaround: Increase the value of vxfs_ninode.The link count table (LCT) file can get damaged such that the flag is set, butthe attribute inode is already freed. In this case, the mount command tries tofree an inode that has been already freed thereby marking the file system fora full structural file system check.Workaround: There is no workaround for this issue.