Installation guide

■
getfacl
■
setfacl
For more information about these functions and utilities, see their respective man pages.
For example, errors might be observed in a network that includes the following conguration:
■
A client that is running Solaris 10 Beta software
■
A server that is running Solaris 10 software
The following table illustrates the results of the ACL functions in client-server congurations
with dierent Solaris 10 releases.
Operation Client S10 OS Server S10 OS Result
get ACL S10 Beta S10 OS fabricated ACL *
get ACL S10 OS S10 Beta works ok
set ACL S10 Beta S10 OS works ok
set ACL S10 OS S10 Beta Error: EOPNOTSUP
Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of
the Solaris 10 OS on both the server and the client.
Access Problems Between Solaris NFSv4 Clients and
NFSv4 Servers
In the current Solaris 10 version, Solaris implementation of NFSv4 Access Control Lists (ACL)
is now compliant with RFC 3530 specications. However, errors occur for NFSv4 clients that
use the Solaris 10 Beta 2 or Beta 1 versions. These clients cannot create les in the NFSv4 servers
that are using the current Solaris 10 release. The following error message is displayed:
NFS getacl failed for server_name: error 9 (RPC: Program/version mismatch)
Workaround: None.
Using mkfs Command to Create File System Might Fail
on Very Large Disks (6352813)
The mkfs command might be unable to create a le system on disks with a certain disk
geometry and whose sizes are greater than 8 Gbytes. The derived cylinder group size is too large
for the 1-Kbyte fragment. The large size of the cylinder group means that the excess metadata
cannot be accommodated in a block.
File Systems
Chapter 2 • Solaris Runtime Issues 63