Veritas File System 5.0 Release Notes, HP-UX 11i v3, First Edition, May 2008

The external quota file would need to be manually migrated as follows:
— On source:
Prior to unmounting the file system, remove the quotas file. Run the fscdsconv
command after unmounting the file system.
— On target:
Mount the file system without quotas. Manually edit the quotas and the quotas.grp
file to enter the limits.
• Problem
Native ACLs will be lost while converting a file system back to the original platform where
ACLs are supported, but VxFS ACLs remain intact.
Workaround
As all target platforms do not support ACLs, converting a file system with ACLs from the
source to a target on which ACLs are not supported results in ACLs not being enabled on
the target. If the file system is converted back to a target on which ACLs are supported,
permission checks are enforced again.
• Problem
CDS validate error is displayed when running in ja_JP.UTF-8-encoded locale.
Workaround
The fscdstask validate command returns an error when files on the specified mount point
have names with ja_JP.eucJP or ja_JP.PCK encodings, and if the locale is changed to
jp_JP.UTF-8.
The following error is displayed:
xargs: Input file is corrupt. : Incorrect byte order
Files must be created with the same locale encoding as the file system on which they reside
as a workaround.
• Problem
Conversion of sparse to Quick I/O files will fail since Oracle tries to write to an unallocated
block.
Workaround
If you try to convert a sparse file to a Quick I/O file, the Oracle instance will fail if Oracle
tries to write into an unallocated block. Specifically, datafiles used by the Oracle8i and
Oracle9i temporary tablespace can be sparse files, so do not convert these to Quick I/O files.
For more information, see the Veritas Storage Foundation for Oracle Administrator’s Guide.
• Problem
The fsck command option -m does not recognize a VxVM volume root partition.
Workaround
The fsck -m command does not recognize a VxVM volume root partition and fails when
the file system is mounted. This occurs because the device id of the block device and the
device id of the character device are different for VxVM volumes.
• Problem
The ncheck command prints special characters such as /...... on file systems containing
pathname exceeding 1024 characters.
Workaround
No workaround is available for this problem.
Known Problems And Workarounds 21