Veritas Storage Foundation and High Availability Solutions Release Notes

About Veritas Storage Foundation and High Availability SolutionsKnown issues65SRL name:SRL size:Total secondaries: 1Secondary:Host name:RVG name:DG name:Data status:Replication status:Current mode:srl1.00 Grvgdg1inconsistentresync in progress (smartsync autosync)asynchronousLogging to: DCM (contains 0 Kbytes) (autosync)Timestamp Information:N/AThe issue is specific to configurations in which primary data volumes have VxFSmounted.Woraround:Use the vxrlink status command to view the number of remaining bytes.Veritas File System known issuesThis section describes the known issues in this release of Veritas File System(VxFS).Taking a FileSnap over NFS multiple times with the same target name canresult in the 'File exists' error (2353352)The "File exists" error occurs as a result of the caching behavior of the NFS client.Because the link operation is successful, the NFS client assumes that a file withthe specified target name, such as file2::snap:vxfs:, was created.. As a result,the NFS client caches a file with this name.Workaround: Remove the target file after a snapshot is created. This forces theNFS client to remove the name from the cache. For example:# ln file1 file2::snap:vxfs:# rm file2::snap:vxfs:Enabling delayed allocation on a small file system sometimes disables thefile system (2389318)When you enable delayed allocation on a small file system, such as around 100MB, the file system can get disabled. In this case, the following error message,displays in the system console log:mesg 001: V-2-1: vx_nospace - file_system file system full(size block extent)