Veritas File System known issues
This section describes the known issues in this release of Veritas File System (VxFS).
Related information
Storage Foundation known issues
Upgrade from InfoScale Enterprise 7.3.1 to 7.4.2 may appear incomplete as the product installer fails to stop the VxFS process (4002728)The VxFS file system with local scope enabled may hang if two or more nodes are restarted simultaneously (3944891)Docker does not recognize VxFS backend file systemWarning message sometimes appear in the console during system startup (2354829)vxresize may fail when you shrink a file system with the \"blocks are currently in use\" error (3762935)On Solaris11U2, /dev/odm may show 'Device busy' status when the system mounts ODMDelayed allocation may be turned off automatically when one of the volumes in a multi-volume file system nears 100%(2438368)The file system deduplication operation fails with the error message \"DEDUP_ERROR Error renaming X checkpoint to Y checkpoint on filesystem Z error 16\" (3348534)Oracle Disk Manager (ODM) may fail to start after upgrade to 7.4.2 on Solaris 11On the cluster file system, clone dispose may failVRTSvxfs verification reports error after upgrading to 7.4.2spfile created on VxFS and ODM may contain uninitialized blocks at the end (3760262)Taking a FileSnap over NFS multiple times with the same target name can result in the 'File exists' error (2353352)On the online cache device you should not perform the mkfs operation, because any subsequent fscache operation panics (3643800)Deduplication can fail with error 110 (3741016)A restored volume snapshot may be inconsistent with the data in the SmartIO VxFS cache (3760219)When in-place and relocate compression rules are in the same policy file, file relocation is unpredictable (3760242)The file system may hang when it has compression enabled (3331276)