Red Hat GLOBAL FILE SYSTEM 4.7 Uživatelská příručka Strana 68

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 134
  • Tabulka s obsahem
  • ŘEŠENÍ PROBLÉMŮ
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 67
Mounting and unmounting Lustre file systems on client nodes4–10
To configure a client node to automatically mount a file system at boot time, perform the following steps:
1. On the client node, create a directory that corresponds to the mount point that was specified for the
file system when it was created, as shown in the following example:
# mkdir /usr/data
2. Create an entry for the Lustre file system either in the /etc/sfstab file on the client node or in the
/etc/sfstab.proto file.
Each time the client node is booted, the file systems specified in the /etc/sfstab file are mounted (with
the exception of any file systems that have the noauto option specified). When the client node is shut down,
all Lustre file systems are unmounted. In addition, you can use the SFS service to mount file systems specified
in the /etc/sfstab file, or to unmount all file systems listed in the /etc/sfstab file at any time (see
Section 4.7).
If you no longer want a file system to be mounted each time the client node is booted, delete (or comment
out) the entry for the file system from the /etc/sfstab file or the /etc/sfstab.proto file. You can
comment out an entry by inserting a # at the start of the line.
4.7.2 Rebuilding the /etc/sfstab file at boot time
You can create a file called /etc/sfstab.proto on the single system image of the client system and
use this file to specify which HP SFS Lustre file systems are to be mounted on the individual client nodes at
boot time. Sections of the /etc/sfstab.proto file can apply to all, or a subset of all, of the client nodes.
When a client node is booted, the SFS service processes the /etc/sfstab.proto file and updates the
contents of the /etc/sfstab file on the client node as appropriate. When the /etc/sfstab file is
processed in turn, the SFS service mounts the specified file systems on the client node.
If the /etc/sfstab.proto file does not exist, the /etc/sfstab file (if one exists) on the client node is
processed as it stands. If an /etc/sfsftab file does not exist on a client node, and the
/etc/sfstab.proto file contains information about file systems to be mounted on that client node, the
SFS service automatically creates the /etc/sfstab file on the client node and copies across the
appropriate sections from the /etc/sfstab.proto file.
The /etc/sfstab file on each client node can also contain information that is specific to that client node.
The SFS service does not overwrite such node-specific information when it updates the /etc/sfstab file
after processing the /etc/sfstab.proto file.
The structure and format of the /etc/sfstab.proto file is as follows:
Comment lines start with # (pound sign) and are ignored, for example:
# This is a comment line.
Directive lines start with #% (pound sign followed by percentage sign) and allow you to specify which
client nodes the information is to be copied to. The following extract shows an example of directive
lines in a client system called delta:
#% ALL Copy on all nodes.
#% delta1 Copy on node delta1 only.
#% delta[1-3,5] Copy on nodes delta1, delta2, delta3, delta5.
The following are examples of mount directives in the /etc/sfstab.proto file:
lnet://35@elan0,34@elan0:/south-mds3/client_elan /usr/data sfs
server=south,fs=data 0 0
lnet://35@elan0,34@elan0:/south-mds4/client_elan /usr/scratch sfs
server=south,fs=scratch 0 0
lnet://35@elan0,34@elan0:/south-mds5/client_elan /usr/test sfs
server=south.fs=test 0 0
As described in Section 4.1, client nodes may be able access an HP SFS system on more than one network.
You must ensure that the entries in the /etc/sfstab.proto file contain the correct information to allow
each client node to access the HP SFS system on the appropriate network.
Zobrazit stránku 67
1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 133 134

Komentáře k této Příručce

Žádné komentáře