Some cells use the Network File System (NFS) in addition to AFS. If you work on an NFS client machine, your system administrator can configure it to access the AFS filespace through a program called the NFS/AFS TranslatorTM. If you have an AFS account, you can access AFS as an authenticated user while working on your NFS client machine. Otherwise, you access AFS as the anonymous user.
|Note:||Acceptable NFS/AFS Translator performance requires that NFS is functioning correctly.|
For you to use the NFS/AFS Translator, your system administrator must configure the following types of machines as indicated:
Your access to AFS is much more extensive if you have an AFS user account. If you do not, the AFS servers recognize you as the anonymous user and only grant you the access available to members of the system:anyuser group.
If your NFS client machine uses an operating system that AFS supports, your system administrator can configure it to enable you to issue many AFS commands on the machine. Ask him or her about the configuration and which commands you can issue.
If you do not have an AFS account or choose not to access AFS as an authenticated user, then all you do to access AFS is provide the pathname of the relevant file. Its ACL must grant the necessary permissions to the system:anyuser group.
If you have an AFS account and want to access AFS as an authenticated user, the best method depends on whether your NFS machine is a supported type. If it is, use the instructions in To Authenticate on a Supported Operating System. If it is not a supported type, use the instructions in To Authenticate on an Unsupported Operating System.
% klog -setpag
% tokensIf you do not have tokens, issue the klog command, which is described fully in To Authenticate with AFS.
% klog -setpag
If your NFS client machine is a system type for which AFS defines a system name, it can make sense to add the -sysname argument. This argument helps the Cache Manager access binaries specific to your NFS client machine, if your system administrator has used the @sys variable in pathnames. Ask your system administrator if this argument is useful for you.
% knfs <host name> [<user ID (decimal)>] \ [-sysname <host's '@sys' value>]
% knfs <host name> [<user ID (decimal)>] -unlog
Acceptable performance by the NFS/AFS translator depends for the most part on NFS. Sometimes, problems that appear to be AFS file server outages, broken connections, or inaccessible files are actually caused by NFS outages.
This section describes some common problems and their possible causes. If other problems arise, contact your system administrator, who can ask the AFS Product Support group for assistance if necessary.
|Note:||To avoid degrading AFS performance, the Cache Manager on the translator machine does not immediately send changes made on NFS client machines to the File Server. Instead, it checks every 60 seconds for such changes and sends them then. It can take longer for changes made on an NFS client machine to be saved than for changes made on an AFS client machine. The save operation must complete before the changes are visible on NFS client machines that are using a different translator machine or on AFS client machines.|
If your system administrator has used the recommended options when creating an NFS mount to an NFS/AFS translator machine, then the mount is both hard and interruptible:
If you have authenticated to AFS and your translator machine reboots, you must issue the klog command (and knfs command, if appropriate) to reauthenticate. If you used the knfs command's -sysname argument to define your NFS client machine's system name, use it again.
This section explains possible meanings for NFS error messages you receive while accessing AFS filespace.
stale NFS client
Getpwd: can't read
Both messages possibly means that your translator machine was rebooted and cannot determine the pathname to the current working directory. To reestablish the path, change directory and specify the complete pathname starting with /afs.
NFS server translator_machine is not responding still trying.
The NFS client is not getting a response from the NFS/AFS translator machine. If the NFS mount to the translator machine is a hard mount, your NFS client continues retrying the request until it gets a response (see Your NFS Client Machine is Frozen). If the NFS mount to the translator machine is a soft mount, the NFS client stops retrying after a certain number of attempts (three by default).