NFS Services Administrator Guide HP-UX 11i v3 HP Part Number: 762805-001 Published: March 2014 Edition: 2
© Copyright 2003, 2014 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license required from HP for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents HP secure development lifecycle......................................................................7 Preface: About this document .........................................................................8 Intended audience....................................................................................................................8 Publishing history......................................................................................................................
Configuring the NFSv4 client protocol version........................................................................35 Deciding between standard-mounted directories and automounted directories............................36 Enabling an NFS client ......................................................................................................36 Mounting remote directories ...............................................................................................
Notes on Direct Maps....................................................................................................62 Sample File Entries for NFS Direct Automounts..................................................................63 Automounting a remote directory using an indirect map..........................................................63 Notes on Indirect Maps.................................................................................................
Forcing a Cache consistency check......................................................................................89 Forcing a consistency check for a specific Mount-Point........................................................89 Forcing a Consistency Check for all the Mount-Points..........................................................89 Unmounting a Cache filesystem...........................................................................................90 Checking the integrity of a cache........
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
Preface: About this document To locate the latest version of this document, go to the HP-UX Networking docs page at: http:// www.hp.com/go/hpux-networking-docs. On this page, select HP-UX 11i v3 Networking Software. This document describes how to configure, and troubleshoot the NFS Services on HP-UX 11i v3. The document printing date and part number indicate the document's current edition. The printing date will change when a new edition is printed.
What's in this document This manual describes how to install, configure and troubleshoot the NFS Services product. The manual is organized as follows: Chapter 1 Introduction Describes the Network File System (NFS) services such NFS, AutoFS, and CacheFS. It also describes new features available with HP-UX 11i v3. Chapter 2 Configuring and Administering NFS Describes how to configure and administer NFS services.
1 Introduction This chapter introduces the Open Network Computing (ONC) services, such as NFS, AutoFS, and CacheFS. This chapter addresses the following topics: • “ONC services overview” (page 10) • “Network File System (NFS)” (page 10) • “New features in NFS” (page 11) ONC services overview Open Network Computing (ONC) services is a technology that consists of core services which enable you to implement distributed applications in a heterogeneous, distributed computing environment.
all the systems on the network, instead of duplicating common directories, such as /usr/local on each system. How NFS works The NFS environment consists of the following components: • NFS Services • NFS Shared Filesystems • NFS Servers and Clients NFS Services The NFS services is a collection of daemons and kernel components, and commands that enable systems with different architectures running different operating systems to share filesystems across a network.
NFSv4 uses the COMPOUND RPC procedure to build sequence of requests into a single RPC. All RPC requests are classified as either NULL or COMPOUND. All requests that are part of the COMPOUND procedure are known as operations. An operation is a filesystem action that forms part of a COMPOUND procedure. NFSv4 currently defines 38 operations. The server evaluates and processes operations sequentially.
the server file tree. If you use the PUTROOTFH operation, the client can traverse the entire file tree using the LOOKUP operation. ◦ Persistent The persistent file handle is an assigned fixed value for the lifetime of the filesystem object that it refers to. When the server creates the file handle for a filesystem object, the server must accept the same file handle for the lifetime of the object. The persistent file handle persists across server reboots and filesystem migrations.
users@domain Or group@domain Where: users specifies the string representation of the user group specifies the string representation of the group domain specifies a registered DNS domain or a sub-domain of a registered domain However, UNIX systems use integers to represent users and groups in the underlying filesystems stored on the disk. As a result, using string identifiers requires mapping of string names to integers and back.
In earlier versions of HP-UX, the exportfs command was used to export directories and files to other systems over a network. Users and programs accessed the exported files on remote systems as if they were part of the local filesystem. NFS disabled the system from exporting directories by using the -u option of the exportfs command. For information on how to share directories with the NFS clients, see “Sharing directories with NFS clients” (page 22).
• Mounting an NFS filesystem through a firewall For information on how to mount an NFS filesystem through a firewall, see “Accessing shared NFS directories across a firewall” (page 29). • Mounting a filesystem securely For information on how to mount a filesystem in a secure manner, see “An example for securely mounting a directory” (page 40). For information on how to disable mount access for a single client, see “Unmounting (Removing) a mounted directory” (page 40).
Consider the following points before enabling client-side failover: • The filesystem must be mounted with read-only permissions. • The filesystems must be identical on all the redundant servers for the failover to occur successfully. For information on identical filesystems, see “Replicated Filesystems” (page 17). • A static filesystem or one that is not modified often is used for failover. • File systems that are mounted using CacheFS are not supported for use with failover.
2 Configuring and administering NFS services This chapter describes how to configure and administer an HP-UX system as an NFS server or an NFS client, using the command-line interface. An NFS server exports or shares its local filesystems and directories with NFS clients. An >NFS client mounts the files and directories exported or shared by the NFS servers. NFS-mounted directories and filesystems appear as a part of the NFS client’s local filesystem.
You can set user and group IDs in the following methods: • Using the HP-UX System Files (/etc/passwd and /etc/group) • Using NIS • Using LDAP Using the HP-UX System Files If you are using the HP-UX system files, add the users and groups to the /etc/passwd and /etc/ group files, respectively. Copy these files to all the systems on the network. For more information on the /etc/passwd and /etc/group files, see passwd(4) and group(4).
Using LDAP For more information on managing user profiles using LDAP, see the LDAP-UX Client Services B.04.00 Administrator’s Guide (J4269-90064). Configuring and administering an NFS server Configuring an NFS server involves completing the following tasks: 1. Identify the set of directories that you want the NFS server to share. For example, consider an application App1 running on an NFS client. Application App1 requires access to the abc filesystem in an NFS server.
Table 3 NFS Server Daemons (continued) Daemon Name Function nfs4srvkd Supports server side delegation. rpc.lockd Supports record lock and share lock operations on the NFS files. rpc.statd Maintains a list of clients that have performed the file locking operation over NFS against the server. These clients are monitored and notified in the event of a system crash.
1069548396 ? 1069640883 ? 0:00 rpc.lockd 0:00 rpc.statd No message is displayed if the daemons are not running. To start the lockd and statd daemons, enter the following command: /sbin/init.d/lockmgr start 4. Enter the following command to run the NFS startup script: /sbin/init.d/nfs.server start The NFS startup script enables the NFS server and uses the variables in the /etc/rc.config.d/nfsconf file to determine which processes to start.
NOTE: Use the bdf command to determine whether your filesystems are on different disks or logical volumes. Each entry in the bdf output represents a separate disk or volume that requires its own entry in the /etc/dfs/dfstab file, if shared. For more information on the bdf command, see bdf(1M). • When you share a directory, the share options that restrict access to a shared directory are applied, in addition to the regular HP-UX permissions on that directory.
nfs Specifies that the filesystem type is NFS -o Enables you to use some of the specific options of the share command, such as sec, async, public, and others. -d Enables you to describe the filesystem being shared When NFS is restarted or the system is rebooted, the /etc/dfs/dfstab file is read and all directories are shared automatically. 2.
In this example, all clients are allowed read-only access to the /tmp directory. The /tmp directory needs to be configured to allow read access to users on the clients. For example, specify -r--r--r-- permissions for the /tmp directory. • Sharing a directory with varying access permissions share -F nfs -o ro=Jan:Feb,rw=Mar /usr/kc In this example, the /usr/kc directory is shared with clients Jan, Feb, and Mar.
Table 4 Security Modes of the share command Security Mode Description sys Uses the default authentication method, AUTH_SYS. The sys mode is a simple authentication method that uses UID/GID UNIX permissions, and is used by NFS servers and NFS clients using the version 2, 3, and 4 protocol. dh Uses the Diffie-Hellman public-key system and uses the AUTH_DES authentication. krb5 Uses Kerberos V5 protocol to authenticate users before granting access to the shared filesystems.
NOTE: In all of this section, the following systems will be used as examples: Kerberos Server: onc52.ind.hp.com NFS Server: onc20.ind.hp.com NFS Client: onc36.ind.hp.com 2. 3. Synchronize the date & time of server nodes with kerberos server. To change the current date and time use date command followed by the current date and time. For example, enter date 06101130 to set the date to June 10th and time to 11:30 AM. The time difference between the systems should not be more than 5 minutes.
9. Re-initialize inetd on NFS servers. inetd –c 10. To create a credential table, enter the following command: onc20# gsscred -m krb5_mech -a 11. Share a directory with the Kerberos security option.
4. Edit the /etc/inetd.conf file and uncomment gssd entry. onc36# cat /etc/inetd.conf | grep gssd rpc 5. xti ticotsord swait root /usr/lib/netsvc/gss/gssd 100234 1 gssd Re-initialize inetd on the NFS servers. onc36# inetd -c 6. To create a credential table, enter the following command: onc36# gsscred -m krb5_mech -a 7.
Shared NFS directories can be accessed across a firewall in the following ways: • Sharing directories across a firewall without fixed port numbers • Sharing directories across a firewall using fixed port numbers in the /etc/default/nfs file • Sharing directories across a firewall using the NFSv4 protocol • Sharing directories across a firewall using the WebNFS feature Sharing directories across a firewall without fixed port numbers (NFSv2 and NFSv3) This is the default method of sharing directories
Where: port_number The port number on which the daemon runs. It can be set to any unique value between 1024 and 65536 for rpc.statd, rpc.mountd and nsf4cbd daemons. STATD_PORT The port on which the rpc.statd daemon runs. MOUNTD_PORT The port on which the rpc.mountd daemon runs. NFS4CBD_PORT The port on which nfs4cbd callback daemon runs. 2. Activate the changes made to the/etc/default/nfs file by restarting the lock manager and NFS server daemons as follows: /sbin/init.d/nfs.server stop /sbin/init.
Table 5 NFS Session versus WebNFS Session (continued) How NFS works across LANs How WebNFS works across WANs client must issue a request for a file handle corresponding to the requested path. Figure 3 shows a sample WebNFS session. Figure 3 WebNFS Session Figure 3 depicts the following steps: 1. An NFS client uses a LOOKUP request with a PUBLIC file handle to access the foo/ index.html file. The NFS client bypasses the portmapper service and contacts the server on port 2049 (the default port). 2.
The /etc/pcnfsd.conf file is read when the pcnfsd daemon starts. If you make any changes to /etc/pcnfsd.conf file while pcnfsd is running, you must restart pcnfsd before the changes take effect. A PC must have NFS client software installed in order to use the system as a PC NFS server. The PCNFS_SERVER variable, configured using the /etc/rc.config.d/nfsconf file controls whether the pcnfsd daemon is started at system boot time.
not removed. These outdated entries can be removed from the export information table by using the -S option with the unshare command. For example, consider that if any application has deleted directory 3 from the shared directory /export/1/2/3 then, unsharing of directory 3 results in an error. For Example, # unshare /export/1/2/3 nfs unshare: /export/1/2/3: No such file or directory In such scenarios, the following unshare command removes this entry from the export information table.
Table 6 NFS client configuration files File Name Function /etc/mnttab Contains the list of filesystems that are currently mounted. /etc/dfs/fstypes Contains the default distributed filesystem type. /etc/fstab Contains the list of filesystems that are automatically mounted at system boot time. Daemons Table 7 describes the NFS client daemons and their functions. Table 7 NFS client daemons Daemon Name Function rpc.lockd Supports record lock and share lock operations on the NFS files. rpc.
For more information on NFSv4, see nfsd(1m), mount_nfs(1m), nfsmapid(1m), and nfs4cbd(1m). Deciding between standard-mounted directories and automounted directories Before you mount any remote directories on a local system, decide whether you want each directory to be standard-mounted or automounted. You can automount directories using AutoFS. For more information on AutoFS, see Chapter 3: “Configuring and administering AutoFS” (page 49).
You can mount a filesystem using the following methods: • Automatic Mounting at System Boot time To set up a filesystem for automatic mounting at system boot time, you must configure it in the /etc/fstab file. All filesystems specified in the /etc/fstab file are mounted during system reboot. • Manual Mounting When you manually mount a filesystem, it is not persistent across reboots or when NFS client restarts.
/opt/nfstest from hpnfsweb:/home/tester Flags: vers=3,proto=udp,sec=sys,hard,intr,link,symlink,acl,devs, rsize=32768,wsize=32768,retrans=5,timeo=11 Attr cache: acregmin=3,acregmax=60,acdirmin=30,acdirmax=60 Lookups: srtt=33 (82ms), dev=33 (165ms), cur=20 (400ms) The directory that you have mounted must be present in this list. For a list of mount options, see mount_nfs(1M).
Figure 4 NFS Mount of manpages • Mounting a Home directory mount -r -o nosuid broccoli:/home/broccoli /home/broccoli mount -r -o nosuid cauliflower:/home/cauliflower /home/cauliflower In this example, the NFS client mounts the home directories from NFS servers broccoli and cauliflower . The nosuid option prevents programs with setuid permission from executing on the local client. Figure 5 illustrates this example.
• Mounting a replicated set of NFS filesystems with same pathnames mount -r onc21,onc23,onc25:/Casey/Clay /Casey/Clay In this example, the NFS client mounts a single filesystem, /Casey/Clay that has been replicated to a number of servers with the same pathnames. This enables the NFS client to failover to either server onc21, onc23, or onc25 if the current server has become unavailable.
To unmount a mounted directory and prevent it from being automatically mounted, follow these steps: Automatic Unmount 1. To check for any processes accessing the mounted directory, enter the following command: fuser -cu mounted_directory 2. To kill the processes, enter the following command: fuser -ck local_mount_point 3. Unmount the filesystem as follows: /usr/sbin/umount mounted_directory 4.
NOTE: TCP is the only transport protocol supported by NFS Version 4. Supporting 1MB transfer for TCP mounts By default, NFS supports 32K transfer sizes across both TCP and UDP transports. To enable support of 1MB transfers for TCP mounts, you must first modify the following tunables: • nfs3_bsize (for NFS version 3) This tunable controls the logical block size used by NFSv3 clients.
The setoncenv command initializes, displays, and removes the value of NFS configuration variables found in either of the following files: • /etc/rc.config.d/nfsconf • /etc/rc.config.d/namesvrs • /etc/default/autofs • /etc/default/keyserv • /etc/default/nfs • /etc/default/nfslogd • /etc/pcnfsd.conf For more information on the setoncenv command, see setoncenv(1M).
and a host in the NIS domain bldg1 shares a directory to the netgroup mydomain, any host in the bldg1 domain may mount the directory, because the host field is blank. If an HP-UX host not running NIS shares a directory to the netgroup mydomain, in this case, the NIS_domain field is ignored but the host field is used. As a result, any host in any domain can mount the directory.
Using Netgroups in configuration files Netgroups may be used in the following files: • /etc/dfs/dfstab, in the [access_list], -rw, -ro, and root list • /etc/hosts.equiv or $HOME/.
Using Netgroups in the /etc/passwd file In the /etc/passwd file, netgroups can be used to indicate whether user information must be looked up in the NIS passwd database. The following sample entry from the /etc/passwd file indicates that users in the netgroup animals must be looked up in the NIS passwd database: +@animals The animals netgroup is defined in the /etc/netgroup file, as follows: animals (-,mickey, ) (-,daffy, ) (-,porky, ) (-,bugs, ) The /etc/passwd file is searched sequentially.
Configuring RPC-based services This section describes the following tasks: • “Enabling other RPC services” (page 47) • “Restricting access to RPC-based services” (page 48) Enabling other RPC services 1. In the /etc/inetd.conf file, use a text editor to uncomment the entries that begin with “rpc” . Following is the list of entries in an /etc/inetd.conf file: #rpc xit tcp nowait root /usr/sbin/rpc.rexd 100017 1 rpc.rexd #rpc dgram udp wait root /usr/lib/netsvc/rstat/rpc.rstatd 100001 2-4 rpc.
Table 9 RPC Services managed by inetd (continued) RPC Service Description rquotad The rpc.rquotad program responds to requests from the quota command, which displays information about a user’s disk usage and limits. For more information, see rquotad (1M) and quota (1). gssd The gssd program operates between the Kernel RPC and the Generic Security Services Application Program Interface (GSS-API) to generate and validate the GSS-API tokens. For more information, see gssd(1M).
3 Configuring and administering AutoFS This chapter provides an overview of AutoFS and the AutoFS environment. It also describes how to configure and administer AutoFS on a system running HP-UX 11i v3.
mounts. The filesystem interacts with the automount command and the automountd daemon to mount filesystems automatically. The automount command This command installs the AutoFS mount-points, and associates an automount map with each mount-point. The AutoFS filesystem monitors attempts to access directories within it and notifies the automountd daemon. The daemon locates a filesystem using the map, and then mounts this filesystem at the point of reference within the AutoFS filesystem.
Maps overview Maps define the mount-points that AutoFS will mount. Maps are available either locally or through a distributed network Name Service, such as NIS or LDAP. AutoFS supports different types of maps. Table 10 lists the different types of maps supported by AutoFS. Table 10 Types of AutoFS Maps Type of Map Description Master Map A master list of maps, which associates a directory with a map. The automount command reads the master map at system startup to create the initial set of AutoFS mounts.
For instance, the NFS server, Basil, exports the /export directory. If you are a user on any of the AutoFS clients, you can use maps to access the /export directory from the NFS server, Basil. AutoFS clients can access the exported filesystem using any one of the following map types: • Direct Map • Indirect Map • Special Map The AutoFS client, Sage, uses a direct map to access the /export directory.
Figure 8 (page 53) illustrates the automounted file structure after the user enters the command. Figure 8 Automounted Directories for On-Demand Mounting Browsability for indirect maps AutoFS now enables you to view the potential mount-points for indirect maps without mounting each filesystem. Consider the following scenario where the AutoFS master map, /etc/auto_master, and the indirect map, /etc/auto_indirect, are on the NFS client, sage.
NFS Loopback mount By default, AutoFS uses the Loopback Filesystem (LOFS) mount for locally mounted filesystems. AutoFS provides an option to enable loopback NFS mounts for the local mount. Use the automountd command with the -L option to enable the loopback NFS mounts for locally mounted filesystems. This option is useful when AutoFS is running on a node that is part of a High Availability NFS environment.
To mount a CD-ROM device, follow these steps: 1. Log in as superuser. 2. Update the appropriate AutoFS map, as follows: cdrom -fstype=hfs, ro :/dev/sr0 For mount devices, If the mount resource begins with a “ / ” , it must be preceded by a colon. For instance in the above section, the CD-ROM device, /dev/sr0, is preceded by the colon. Supported backends (Map Locations) AutoFS maps can be located in the following: • Files: Local files that store the AutoFS map information for that individual system.
1. If the AutoFS maps are not already migrated, migrate your AutoFS maps to LDAP Directory Interchange Format (LDIF) files using the migration scripts. The migrated maps can also be used if you have chosen the older schema. For information on the specific migration scripts, see LDAP-UX Client Services B.04.10 Administrator’s Guide (J4269-90067). 2. Import the LDIF files into the LDAP directory server using the ldapmodify tool.
the directory is mounted the next time. However, if you change the local directory name in the direct or indirect map, or if you change the master map, these changes do not take effect until you run the automount command to force AutoFS to reread its maps. Updating from automounter to AutoFS Automounter is a service that automatically mounts filesystems on reference. The service enables you to access the filesystems without taking on the superuser role and use the mount command.
AutoFS configuration changes This section describes the various methods to configure your AutoFS environment. Configuring AutoFS using the nfsconf file You can use the /etc/rc.config.d/nfsconf file to configure your AutoFS environment. The /etc/rc.config.d/nfsconf file is the NFS configuration file. This file consists of the following sets of variables or parameters: 1. Core Configuration Variables 2. Remote Lock Manager Configuration Variables 3. NFS Client and Server Configuration Variables 4.
Configuring AutoFS using the/etc/default/autofs file You can also use the /etc/default/autofs file to configure your AutoFS environment. The /etc/default/autofs file contains parameters for the automountd daemon and the automount command. Initially, the parameters in the /etc/default/autofs file are commented. You must uncomment the parameter to make the value for that parameter take effect.
the initial set of AutoFS mounts. Subsequent to system startup, the automount command maybe run to install AutoFS mounts for new entries in the master map or a direct map, or to perform unmounts for entries that have been removed from these maps. Following is a syntax of an auto_master file: mount-point map-name [mount-options] where: mount-point Directory on which an AutoFS mount is made. map-name Map associated with mount-point specifying locations of filesystems to mount.
Table 13 Direct Versus Indirect AutoFS Map Types (continued) Direct Map Indirect Map internal mount table, /etc/mnttab. This can cause the mount table to become very large. mount table, /etc/mnttab. Additional entries are created when the directories are actually mounted. The mount table takes up no more space than necessary, because only mounted directories appear in it. Configuring AutoFS direct and indirect mounts A direct map is an automount mount-point.
/- 2. direct_map_name [mount_options] If you are using local files for maps, use an editor to open or create a direct map in the /etc directory. The direct map is commonly called /etc/auto_direct. Add an entry to the direct map with the following syntax: local_directory [mount_options] server:remote_directory If you are using NIS or LDAP to manage maps, add an entry to the direct map on the NIS master server or the LDAP directory. 3. 4.
remote server:directory Location of the directory, on the server, that is to be mounted. If you plan to use NIS or LDAP to manage maps, there can be only one direct map in your configuration. If the direct map name in the master map begins with a slash (/), AutoFS considers it to be a local file. If it does not contain a slash, AutoFS uses the NSS to determine whether it is a file, LDAP, or an NIS map. For more information on using NSS, see nsswitch.conf(4).
local_parent_directory indirect_map_name [mount_options] 2. If you are using local files for your AutoFS maps, use an editor to open or create an indirect map in the /etc directory. Add a line with the following syntax, to the indirect map: local_subdirectory [mount_options] server:remote_directory If you are using NIS or LDAP to manage maps, add an entry to an indirect map on the corresponding NIS master server or the LDAP directory. 3. 4.
Following are sample lines from the AutoFS master map on the NFS client, sage. The master map also includes an entry for the /etc/auto_direct direct map. # /etc/auto_master file # local mount-point //nfs/desktop map name mount options /etc/auto_direct /etc/auto_desktop The local_parent_directory specified in the master map consists of directories, except the lowest-level subdirectory in the local directory pathname.
When AutoFS starts up on the host sage, it assigns the value sage to the HOST variable. When you request access to the local /private_files directory on sage, AutoFS mounts /export/private_files/sage from basil. To use environment variables as shortcuts in direct and indirect maps, follow these steps: 1.
* basil:/export/home/& The user's home directory is configured in the /etc/passwd file as /home/username. For example, the home directory of the user terry is /home/terry. When Terry logs in, AutoFS looks up the /etc/auto_home map and substitutes terry for both the asterisk and the ampersand. AutoFS then mounts Terry’s home directory from /export/home/terry on the server, basil, to /home/terry on the local NFS client.
Example of automounting a user’s home directory User Howard’s home directory is located on the NFS server, basil, where it is called /export/home/howard.
If you are using NIS to manage AutoFS maps, add the previous entry to the master map file on the NIS master server. Rebuild the map and push it out to the slave servers. For more information on NIS and NIS maps, see the NIS Administrator’s Guide (5991-2187). If you are using LDAP, add the entry to the LDAP directory. 2.
Figure 14 Automounted Directories from the -hosts Map—Two Servers Turning off an AutoFS map using the -null map To turn off a map using the -null map, follow these steps: 1. Add a line with the following syntax in the AutoFS master map: local_directory -null 2. If AutoFS is running, enter the following command on each client that uses the map, to force AutoFS to reread its maps: /usr/sbin/automount This enables AutoFS to ignore the map entry that does not apply to your host.
!/bin/sh Server=$1 showmount -e $1 | awk ‘NR > 1 {print $1 “\t'$Server’:” $1 ” \\ “}’ | sort Advanced AutoFS administration This section presents advanced AutoFS concepts that enable you to improve mounting efficiency and also help make map building easier.
another network segment, regardless of the weight you assign. The weighting factor is taken into account only when deciding between servers with the same network proximity. • If the remote directory has a different name on different servers, use a syntax such as the following from a direct map: /nfs/proj2/schedule -ro \ broccoli:/export/proj2/schedule, \ cauliflower:/proj2/FY07/schedule To configure multiple replicated servers for a directory, follow these steps: 1.
If the list of multiple servers contains a combination of servers that includes all versions of the NFS protocol, then AutoFS selects a subset of servers with the highest NFS protocol version configured. For example, a list contains a number of servers configured with the NFSv4 protocol, and a few servers configured with the NFSv2 protocol. AutoFS will use the subnet of servers configured with the NFSv4 protocol, unless a server configured with the NFSv2 protocol is closer.
releases tools source projects -fstype=autofs -fstype=autofs bigiron:/export/releases mickey,minnie:/export/tools auto_eng_source auto_eng_projects A user in the blackhole project within engineering can use the following path: /org/eng/projects/blackhole Starting with the AutoFS mount at /org, the evaluation of this path dynamically creates additional AutoFS mounts at /org/eng and /org/eng/projects.
The following example shows an indirect map configuration: # /etc/auto_master file # local mount-point map name mount options /nfs/desktop /etc/auto_desktop # /etc/auto_desktop file # local mount-point mount options remote server:directory draw write -nosuid -nosuid thyme:/export/apps/draw basil:/export/write Enter the following commands: cd /nfs/desktop ls The ls command displays the following output: draw write The draw and write subdirectories are the potential mount-points (browsability), but a
/usr/sbin/fuser -ck local_mount_point 4. To stop AutoFS, enter the following command: /sbin/init.d/autofs stop IMPORTANT: Do not stop the automountd daemon with the kill command. It does not unmount AutoFS mount-points before it terminates. Use the autofs stop command instead. 5.
To Stop AutoFS Logging To stop AutoFS logging, stop AutoFS and restart it after removing the “-v” option from AUTOMOUNTD_OPTIONS. AutoFS tracing AutoFS supports the following Trace levels: Detailed (level 3) Includes traces of all the AutoFS requests and replies, mount attempts, timeouts, and unmount attempts. You can start level 3 tracing while AutoFS is running. Basic (level 1) Includes traces of all the AutoFS requests and replies. You must restart AutoFS to start level 1 tracing.
This command lists the process IDs and user names of all users who are using the mounted directory. 5. Warn users to exit the directory, and kill processes that are using the directory, or wait until all the processes terminate. Enter the following command to kill all the processes using the mounted directory: /usr/sbin/fuser -ck local_mount_point 6. Enter the following command to stop AutoFS: /sbin/init.d/autofs stop CAUTION: Do not kill the automountd daemon with the kill command.
May 13 18:45:09 t5 May 13 18:45:09 t5 May 13 18:45:09 t5 args_temp: hpnfs127, , 0x3004060, 0, 0, 0, 0,0, 0, 0, 0, hpnfs127:/tmp mount hpnfs127:/tmp dev=44000004 rdev=0 OK MOUNT REPLY: status=0, AUTOFS_DONE Unmount Event Tracing Output The general format of an unmount event trace is: UNMOUNT REQUEST:
Another workaround is to force the filesystem to remain busy by opening a temporary file, so that AutoFS cannot unmount it.
4 Configuring and administering a cache filesystem This chapter introduces the Cache Filesystem (CacheFS) and the CacheFS environment. It also describes how to configure and administer CacheFS on a system running HP-UX 11i v3.
cold cache A cache that has not yet been populated with data from the back filesystem is called cold cache. cache miss An attempt to reference data that is not yet cached is called a cache miss. warm cache A cache that contains data in its front filesystem is called a warm cache. In this case, the cached data can be returned to the user without requiring an action from the back filesystem. cache hit A successful attempt to reference data that is cached is called a cache hit.
Features of CacheFS This section discusses the features that CacheFS supports on systems running HP-UX 11i v3. • Cache Pre-Loading via the “cachefspack” Command The cachefspack command enables you to pre-load or pack specific files and directories in the cache, thereby improving the effectiveness of CacheFS. It also ensures that current copies of these files are always available in the cache. Packing files and directories in the cache enables you to have greater control over the cache contents.
• Support for Large Files and Large Filesystems CacheFS supports the maximum file and filesystem sizes supported by the underlying front filesystem and the back filesystem. CacheFS data structures are 64-bit compliant. • Support for ACLs An Access Control List (ACL) offers stronger file security by enabling the owner of the file to define file permissions for specific users and groups. This version of CacheFS on HP-UX supports ACLs with VxFS and NFS and not with HFS.
For example to create a CacheFS directory called /disk2/cache using the following command: cfsadmin -c /disk2/cache This creates a new directory called cache under the /disk2 directory. CacheFS allows more than one filesystem to be cached in the same cache. You need not create a separate cache directory for each CacheFS mount. Mounting an NFS filesystem using CacheFS This section describes how to mount an NFS filesystem using CacheFS.
To change the mount option from noconst to the default option, without deleting or rebuilding the cache, enter the following commands: umount /mnt1 mount -F cachefs -o backfstype=nfs,cachedir=/cache CFS1:/tmp /mnt1 To change the mount option from default to weakconst after unmounting, enter the following command: mount -F cachefs -o backfstype=nfs,cachedir=/cache,weakconst CFS2:/tmp /mnt1 For more information on the various mount options of the CacheFS filesystem, see mount_cachefs(1M).
/tmp/logfile Specifies the logfile to be used. NOTE: When multiple mount-points use the same cache directory, enabling logging for one CacheFS mount-point automatically enables logging for all the other mount-points. 3. To verify if logging is enabled for /cfs_mnt1, enter the following command: cachefslog /cfs_mnt1 If logging has been enabled, the logfile is displayed. Disabling logging in CacheFS You can use the cachefslog command to halt or disable logging for a CacheFS mount-point.
Packing a Cached filesystem Starting with HP-UX 11i v3, the cachefspack command is introduced to provide greater control over the cache. This command enables you to specify files and directories to be loaded, or packed, in the cache. It also ensures that the current copies are always available in the cache.
packing-list Specifies the name of the packing-list file. The files specified in the packing list are now packed in the cache. You can unpack files that you no longer require, using one of the following methods: • Using the -u option To unpack a specific packed file or files from the cache directory, enter the following command: cachefspack -u filename where: -u Specifies that certain files are to be unpacked. filename Specifies the file to unpack.
Unmounting a Cache filesystem To unmount a Cache filesystem, enter the following command: umount mount-point where: mount-point Specifies the CacheFS mount-point that you want to unmount. Checking the integrity of a cache You can use the fsck command to check the integrity of a cache. The CacheFS version of the fsck command checks the integrity of the cache and automatically corrects any CacheFS problems that it encounters.
Table 14 CacheFS Resource Parameters (continued) CacheFS Resource Parameter Default Value minfiles 0 threshfiles 85 For more information on the resource parameters, see cfsadmin(1M). You can update the resource parameters using the -u option of the cfsadmin command. NOTE: All filesystems in the cache directory must be unmounted when you use the -u option. Changes will be effective the next time you mount any filesystem in the specified cache directory.
mount | grep -w "cachedir=/disk2/cache" | awk '{print $1}' An output similar to the following is displayed if CacheFS mount-points are using the cache directory: /mnt /mnt1 3. To unmount the CacheFS mount-points, /_mnt, and /_mnt1, enter the following commands: umount /mnt umount /mnt1 4. To delete the CacheFS filesystem corresponding to the Cache ID from the specified cache directory, enter the following command: cfsadmin -d CacheID cache-directory 5.
modifies: 85727 garbage collection: 0 You can run the cachefsstat command with the -z option to reinitialize CacheFS statistics. You must be a superuser to use the -z option. NOTE: If you do not specify the CacheFS mount-point, statistics for all CacheFS mount-points are displayed. For more information about the cachefsstat command, see cachefsstat(1M).
Table 15 Common Error Messages encountered while using the cfsadmin command Error Message Possible Causes “cfsadmin: Cannot create lock file /test/ mnt/c/.cfs_lock” Indicates that you do not have write 1. Delete the cache. permissions to the filesystem, where 2. Recreate the cache directory the cache directory is being using the cfsadmin command. created. “mount failed No space left on device” The Cache directory may not be clean.
5 Troubleshooting NFS services This chapter describes tools and procedures for troubleshooting the NFS Services. This chapter addresses the following topics: • “Common problems with NFS” (page 95) • “Performance tuning” (page 102) • “Logging and tracing of NFS services” (page 104) Common problems with NFS This section lists the following common problems encountered with NFS and suggests ways to correct them.
On the NFS server, check if the following processes are running: ◦ nfsd ◦ rpc.mountd ◦ rpc.statd ◦ rpc.lockd If any of these processes is not running, follow these steps: 1. Make sure the /etc/rc.config.d/nfsconf file on the NFS server contains the following lines: NFS_SERVER=1 START_MOUNTD=1 2. Enter the following command on the NFS server to start all the necessary NFS processes: /sbin/init.d/nfs.server start □ Enter the following command on the NFS client to make sure the rpc.
“Access Denied” message □ Enter the following command on the NFS client to check that the NFS server is exporting the directory you want to mount: /usr/sbin/showmount -e server_name If the server is not exporting the directory, edit the /etc/dfs/dfstab file on the server so that it allows your NFS client access to the directory. Then, enter the following command to force the server to read its /etc/dfs/dfstab file.
“Device Busy” message □ If you received the “device busy” message while attempting to mount a directory, check whether it is already mounted. □ If you received the “device busy” message while attempting to unmount a directory, a user or process is currently using the directory. Wait until the process completes, or follow these steps: 1.
files another user is accessing. For more information on the source code control system, see rcsintro(5). □ If someone has restored the server’s file systems from backup or entered the fsirand command on the server, follow these steps on each of the NFS clients to prevent stale file handles by restarting NFS: 1. Enter the mount(1M) command with no options, to get a list of all the mounted file systems on the client: /usr/sbin/mount 2.
3. Enter the following commands to verify that rpc.statd, rpc.lockd, and nfsd are all running and responding to RPC requests: /usr/bin/rpcinfo /usr/bin/rpcinfo /usr/bin/rpcinfo /usr/bin/rpcinfo /usr/bin/rpcinfo /usr/bin/rpcinfo 4. 5. -u -u -u -u -u -u servername servername servername clientname clientname clientname status nlockmgr nfs status nlockmgr nfs Before retrying the mount that caused the program to hang, wait for a short while, say two minutes. If the problem persists, restart rpc.
“Permission Denied” message This message could be displayed because of one of the following reasons: • The Ticket Granting Ticket (TGT) has expired To renew the ticket, enter the following command: kinit username • Fully qualified hostname resolution problem To verify the hostname resolution, check the following files: ◦ /etc/nsswitch.conf ◦ /etc/hosts To provide a fully qualified host name, do the following: • ◦ Add dns in the host entry in the /etc/nsswitch.
If the default principal name is not ‘guest’, enter the following command to obtain a TGT for the guest principal: kinit guest Performance tuning This section gives suggestions for identifying performance problems in your network and improving NFS performance on your servers and clients.
On the NFS clients that require access to the linked directory, mount the target of the link. Then, remove the link from the exported directory on the server. When a client requests access to a linked file or directory, two requests are sent to the server: one to look up the path to the link, and another to look up the target of the link. You can improve NFS performance by removing symbolic links from exported directories.
Logging and tracing of NFS services This section tells you how to start the following tools: • “AutoFS logging” (page 76) • “AutoFS tracing” (page 77) • “Logging for the other NFS services” (page 104) • “Logging with nettl and netfmt” (page 104) • “Tracing with nettl and netfmt” (page 105) Logging for the other NFS services You can configure logging for the following NFS services: • rpc.rexd • rpc.rstatd • rpc.rusersd • rpc.rwalld • rpc.sprayd Logging is not available for the rpc.
/usr/sbin/nettl -start 2. Enter the following command to start logging: /usr/sbin/nettl -l i w e d -e all The logging classes are specified following the -l option. They are i (informational), w (warning), e (error), and d (disaster). Disaster logging is always on. You cannot turn it off. Information logging (i) fills up your logfile faster than the other classes, so you might want to leave it off. 3. 4. Recreate the event you want to log.
6 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index Symbols D + (plus sign) in AutoFS maps, 73 in group file, 46 in passwd file, 46 -hosts map, 36, 68 examples, 69 -null map, 70 32k transfer size, 42 device busy, 98 direct map, 61 advantages, 60 environment variables in, 66 examples, 63 modifying, 57 DNS, 96 A environment variables in AutoFS maps, 66 /etc/auto_master file see auto_master map, 68 /etc/group file see group database, 19 /etc/netgroup file see netgroup file, 43 /etc/rc.config.d/namesvrs file see namesvrs file, 21 /etc/rc.config.
wildcards in, 66, 67 inetd.conf file, 47, 96, 104 inetd.
logging, 104 rwalld logging, 104 wildcards in AutoFS maps, 66, 67 wsize mount option, 102, 103 S ypmake, 43 Y security in mounted directories, 39 server not responding, NFS, 95, 103 server, NFS, 18 CPU load, 102 too slow, 102 showmount, 97 SIGUSR2 signal to automount, 77 simultaneous mounts, AutoFS, 71 slow server, NFS, 102 soft mount timed out, 103 soft mount option, 100, 103 sprayd logging, 104 stale file handle, 98 avoiding, 99 standard mount, 37 START_MOUNTD variable, 96 statd, 95 checking for hung
