VERITAS File System 4.1 Release Notes (June 2006)

VERITAS File System 4.1 Release Notes
Software Issues in Base-VXFS
Chapter 122
While performing a full fsck, the system keeps certain data structures in the core for
validating the space usage and inode usage. The space needed depends on the number of
inodes and the number of blocks in the file system. The fsck command needs
approximately 16 MB per 1 TB for an 8K block size file system (128 MB per 1 TB for a 1K
block size file system) and 32 MB per million inodes. Sufficient memory and swap space
should be configured on the system before running a full fsck on a large file-enabled
system.
A replay fsck does not need a significant amount of memory and does not have these
issues.
• Some Disk Quota Operations Do Not Function on NFS
When VxFS file systems are exported via NFS, quotas on the file system apply to users
when accessing the file system from NFS clients. However, the HP-UX quota commands
on the NFS client cannot be used to edit quotas. The VxFS quota commands can be used
on the server to edit quotas.
• Files and Directories
To maximize VxFS performance, do not exceed 100,000 files in the same directory. Use
multiple directories instead.
• Cross-Platform Data Sharing (CDS)
— External Quota File
CDS does not support converting the external quota file. 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.
— Handling ACLs with CDS
Because not all target platforms 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.
• Quick I/O Files Cannot Be Sparse Files