VERITAS Storage Foundation 4.1 Release Notes

VERITAS Storage Foundation Release Notes
Software Issues
43
Non-standard Command Behavior When Using ACLs
The output of the ls -l command on VxFS file systems shows mask/CLASS_OBJ in place of
group permissions if Access Control Lists (ACLs) are in use on a file or a directory. You can
determine the effective group permissions by using the getacl command. In the next release of
VxFS, the behavior of ls -l will show effective group permissions, that is, GROUP_OBJ masked
by CLASS_OBJ.
The chmod command changes mask/CLASS_OBJ instead of the group permissions if ACLs are
in use on a file or a directory. GROUP_OBJ is not changed by chmod, and because effective group
permissions are determined by GROUP_OBJ and CLASS_OBJ, the default group may not receive
the permissions specified by chmod. Because ls -l shows mask only (which is changed by
chmod), it only appears that the group permissions are changed as specified in chmod. Use of the
chmod command is not advisable on files with ACLs. Instead, use the getacl command to
manipulate permissions.
In the next release of VxFS, the behavior of both mask/CLASS_OBJ and GROUP_OBJ will be to
change after executing the chmod command. Even in that case, using the getacl command is
advisable for manipulating permissions.
Even if the parent directory has default ACLs, umask is applied to a newly created file. According
to POSIX standards, umask should be applied only if the parent directory does not have any
default ACLs. In the next release of VxFS, this behavior will be made POSIX compliant.
See the following manual pages for ACL-related information: aclsort(3C), chmod(1),
getacl(1), ls(1), setacl(1), and uname(1).
The newfs -R Command Allows Reserving Swap Space Larger Than the
Device
The newfs -R command will reserve swap space greater than is available on the underlying
device. This problem will be addressed in a future patch release from HP.
Large Files Should Be Mounted Only on Systems With Sufficient Memory
When a file system is mounted, VxFS keeps certain data structures in the kernel. As the size of the
file system increases, the amount of data structures stored by VxFS also increases. The file system
typically keeps approximately 128 bytes per allocation unit (32,768 file system blocks). This
translates to a usage of 512K per 1 TB for an 8K block size file system (4 MB per 1 TB for a 1K