VERITAS Storage Foundation 4.1 Release Notes

Software Issues
42 VERITAS Storage Foundation Release Notes
As a workaround this issue can be avoided by passing a sufficiently large user buffer.
File System With Quotas Cannot Be Mounted After Doing CDS Conversion
If a file system is using quotas, it cannot be mounted with quotas turned on after converting the
byte order of the file system with the fscdsconv(1M) utility. Similarly, quotas cannot be turned
on, if the converted file system is first mounted with quotas turned off. See the fscdsconv(1M)
manual page for the workaround.
CDS Validate Error Running in ja_JP.UTF-8-Encoded Locale
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, but the locale has been changed to
jp_JP.UTF-8. The error is as follows:
xargs: Input file is corrupt. : Incorrect byte order
Files should be created with the same locale encoding as the file system on which they reside.
Data Integrity Issues with Disks and Disk Arrays with Write-back Caches
Disk drives configured to use a write-back cache, or disk arrays configured with a volatile
write-back cache, exhibit data integrity problems. The problems occur after a power failure, SCSI
bus reset, or other event in which the disk has cached data, but has not yet written it to non-volatile
storage. Contact your disk drive or disk array manufacturer to determine whether your disk drives
use a write-back cache, and if the configuration can be changed to disable write-back caching.
Under Some Conditions, fsadm Cannot Truncate a Directory
The fsadm command cannot truncate a directory if it has only one extent that is more than two
blocks in length, even if all the directory entries are deleted.
Inode Limitation on File Systems Without Large File Support
For a file system to have more than 8 million inodes, you must create it using the largefiles
option of mkfs (the fsadm utility can also be used to set the largefiles flag on the file
system). See the mkfs_vxfs(1M) and fsadm_vxfs(1M) manual pages for details. The
largefiles option is enabled by default on VxFS 4.1. In previous VxFS releases,
nolargefiles was the default mount option.