1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Using the NFS/AFS Translator</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="AFS User Guide"
11 HREF="book1.html"><LINK
13 TITLE="Troubleshooting"
14 HREF="c3402.html"><LINK
16 TITLE="AFS Command Syntax and Online Help"
17 HREF="a3812.html"></HEAD
28 SUMMARY="Header navigation table"
37 >AFS User Guide: Version 3.6</TH
74 >Appendix A. Using the NFS/AFS Translator</H1
84 cells use the Network File System (NFS) in addition to AFS. If you work on an NFS client machine, your system
85 administrator can configure it to access the AFS filespace through a program called the <SPAN
94 >. If you have an AFS account, you can access AFS as an
95 authenticated user while working on your NFS client machine. Otherwise, you access AFS as the
110 >Acceptable NFS/AFS Translator performance requires that NFS is functioning correctly.</P
119 >Requirements for Using the NFS/AFS Translator</A
125 For you to use the NFS/AFS Translator, your system
126 administrator must configure the following types of machines as indicated:</P
134 >NFS/AFS translator machine</I
136 > is an AFS client machine that also acts as an
137 NFS server machine. Its Cache Manager acts as the surrogate Cache Manager for your NFS client machine. Ask your
138 system administrator which translator machines you can use.</P
142 >Your NFS client machine must have an NFS mount to a translator machine. Most often, your system
143 administrator mounts the translator machine's <SPAN
149 > directory and names the mount
156 > as well. This enables you to access the entire AFS filespace using standard
157 AFS pathnames. It is also possible to create mounts directly to subdirectories of
164 >, and to give NFS mounts different names on the NFS client
169 >Your access to AFS is much more extensive if you have an AFS user account. If you do not, the AFS servers
170 recognize you as the <SPAN
176 > user and only grant you the access available to
185 >If your NFS client machine uses an operating system that AFS supports, your system administrator can
186 configure it to enable you to issue many AFS commands on the machine. Ask him or her about the configuration and
187 which commands you can issue.</P
195 >Accessing AFS via the Translator</A
198 >If you do not have an AFS account or choose not to access AFS as an authenticated user, then all you do to
199 access AFS is provide the pathname of the relevant file. Its ACL must grant the necessary permissions to the
208 >If you have an AFS account and want to access AFS as an authenticated user, the best method depends on
209 whether your NFS machine is a supported type. If it is, use the instructions in <A
210 HREF="a3632.html#HDRWQ82"
212 Authenticate on a Supported Operating System</A
213 >. If it is not a supported type, use the instructions in
215 HREF="a3632.html#HDRWQ83"
216 >To Authenticate on an Unsupported Operating System</A
224 >To Authenticate on a Supported Operating System</A
230 >Log into the NFS client machine using your NFS username.</P
234 > Issue the <SPAN
240 > command. For complete instructions, see
242 HREF="c569.html#HDRWQ29"
243 >To Authenticate with AFS</A
246 CLASS="programlisting"
266 >To Authenticate on an Unsupported Operating System</A
272 >Log onto the NFS client machine using your NFS username.</P
279 >Establish a connection to the NFS/AFS translator machine you are
280 using (for example, using the <SPAN
286 > utility) and log onto it using your AFS
287 username (which is normally the same as your NFS username).</P
291 > If the NFS/AFS translator machine uses an AFS-modified login utility, then you obtained AFS tokens in Step
293 HREF="a3632.html#LINFS-TELNET"
295 >. To check, issue the <SPAN
302 which is described fully in <A
303 HREF="c569.html#HDRWQ30"
304 >To Display Your Tokens</A
307 CLASS="programlisting"
317 If you do not have tokens, issue the <SPAN
323 > command, which is described fully in
325 HREF="c569.html#HDRWQ29"
326 >To Authenticate with AFS</A
329 CLASS="programlisting"
352 > command to associate your AFS tokens
353 with your UNIX UID on the NFS client machine where you are working. This enables the Cache Manager on the
354 translator machine to use the tokens properly when you access AFS from the NFS client machine.
357 >If your NFS client machine is a system type for which AFS defines a system name, it can make sense
364 > argument. This argument helps the Cache Manager access
365 binaries specific to your NFS client machine, if your system administrator has used the
372 > variable in pathnames. Ask your system administrator if this argument is useful for
379 CLASS="programlisting"
391 >user ID (decimal)</VAR
401 >host's '@sys' value</VAR
422 >Specifies the fully-qualified hostname of your NFS client machine (such as
444 >Specifies your UNIX UID or equivalent (not your username) on the NFS client machine. If your
445 system administrator has followed the conventional practice, then your UNIX and AFS UIDs are the same. If you
446 do not know your local UID on the NFS machine, ask your system administrator for assistance. Your system
447 administrator can also explain the issues you need to be aware of if your two UIDs do not match, or if you
448 omit this argument.</P
460 >Specifies your NFS client machine's system type name.</P
477 translator machine, but do not unauthenticate.</P
481 >Work on the NFS client machine, accessing AFS as necessary.</P
485 > When you are finished accessing AFS, issue the <SPAN
491 > command on the translator
492 machine again. Provide the same <VAR
499 arguments as in Step <A
500 HREF="a3632.html#LINFS-KNFS"
509 flag to destroy your tokens. If you logged out from the translator machine in Step
511 HREF="a3632.html#LINFS-LOGOUT"
513 >, then you must first reestablish a connection to the translator machine
515 HREF="a3632.html#LINFS-TELNET"
519 CLASS="programlisting"
531 >user ID (decimal)</VAR
552 >Troubleshooting the NFS/AFS Translator</A
555 >Acceptable performance by the NFS/AFS translator depends for the most part on NFS. Sometimes, problems that
556 appear to be AFS file server outages, broken connections, or inaccessible files are actually caused by NFS
559 >This section describes some common problems and their possible causes. If other problems arise, contact your
560 system administrator, who can ask the AFS Product Support group for assistance if necessary.</P
568 >To avoid degrading AFS performance, the Cache Manager on the translator machine does not immediately
569 send changes made on NFS client machines to the File Server. Instead, it checks every 60 seconds for such
570 changes and sends them then. It can take longer for changes made on an NFS client machine to be saved than for
571 changes made on an AFS client machine. The save operation must complete before the changes are visible on NFS
572 client machines that are using a different translator machine or on AFS client machines.</P
581 >Your NFS Client Machine is Frozen</A
584 >If your system administrator has used the recommended options when creating an NFS mount to an NFS/AFS
585 translator machine, then the mount is both <SPAN
601 >A hard mount means that the NFS client retries its requests if it does not receive a response
602 within the expected time frame. This is useful because requests have to pass through both the NFS and AFS client
603 software, which can sometimes take longer than the NFS client expects. However, it means that if the NFS/AFS
604 translator machine actually becomes inaccessible, your NFS client machine can become inoperative
621 >If the NFS mount is interruptible, then in the case of an NFS/AFS translator machine outage you
628 >> or another interrupt signal to halt the NFS client's
629 repeated attempts to access AFS. You can then continue to work locally, or can NFS-mount another translator
630 machine. If the NFS mount is not interruptible, you must actually remove the mount to the inaccessible translator
641 >NFS/AFS Translator Reboots</A
644 >If you have authenticated to AFS and your translator machine reboots, you must issue the
657 > command, if appropriate)
658 to reauthenticate. If you used the <SPAN
671 > argument to define your NFS client machine's system name, use it
680 >System Error Messages</A
683 >This section explains possible meanings for NFS error messages you receive while accessing AFS
687 CLASS="computeroutput"
688 >stale NFS client</SAMP
692 CLASS="computeroutput"
693 >Getpwd: can't read</SAMP
696 >Both messages possibly means that your translator machine was rebooted and cannot determine the pathname to
697 the current working directory. To reestablish the path, change directory and specify the complete pathname starting
707 CLASS="computeroutput"
710 >translator_machine</VAR
711 > is not responding still
715 >The NFS client is not getting a response from the NFS/AFS translator machine. If the NFS mount to the
716 translator machine is a hard mount, your NFS client continues retrying the request until it gets a response (see
718 HREF="a3632.html#HDRWQ85"
719 >Your NFS Client Machine is Frozen</A
720 >). If the NFS mount to the translator machine is a
721 soft mount, the NFS client stops retrying after a certain number of attempts (three by default).</P
730 SUMMARY="Footer navigation table"
779 >AFS Command Syntax and Online Help</TD