Veritas File System known issues

Last published : Sep 09, 2026
This section describes the known issues in this release of Veritas File System (VxFS).
Related information
Storage Foundation known issues
The fsmap -N command fails for an inode or file that contains extended attributes (4003019)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 systemDelayed 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)The fsappadm subfilemove command moves all extents of a filedchunk_enable does not get set through vxtunefs in AIX (3551030)Cannot use some commands from inside an automounted Storage Checkpoint (2490709)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)You are unable to unmount the NFS exported file system on the server if you run the fsmigadm command on the client (2355258)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)Unaligned large reads may lead to performance issues (3064877)