Red Hat GLOBAL FILE SYSTEM 4.7 Guide de l'utilisateur télécharger pdf (Page 67)

Using the SFS service 4–9

An alternative method of unmounting Lustre file systems on the client node is to enter the service sfs

stop command, as described in Section 4.7. However, note that when you run the service sfs stop

command, only the file systems specified in the /etc/sfstab file are unmounted. File systems that were

mounted manually are not unmounted.

4.7 Using the SFS service

This section is organized as follows:

• Mounting Lustre file systems at boot time (Section 4.7.1)

• Rebuilding the /etc/sfstab file at boot time (Section 4.7.2)

• The service sfs start command (Section 4.7.3)

• The service sfs reload command (Section 4.7.4)

• The service sfs stop command (Section 4.7.5)

• The service sfs status command (Section 4.7.6)

• The service sfs cancel command (Section 4.7.7)

• The service sfs help command (Section 4.7.8)

• Disabling and enabling the SFS service (Section 4.7.9)

For more information on the SFS service commands, see the sfstab(8), manpage.

4.7.1 Mounting Lustre file systems at boot time

NOTE: To be able to mount Lustre file systems, the client node must be configured as described in

Chapter 2 or Chapter 3. In particular, the client node must have an options lnet setting configured in

the /etc/modprobe.conf.lustre or /etc/modules.conf.lustre file.

The /etc/sfstab file on each client node is used to specify which Lustre file systems are to be mounted

each time the node is booted. There must be one entry in this file for each Lustre file system that is to be

automatically mounted when the node is booted. You can create entries in the /etc/sfstab file manually,

and you can also update the file dynamically at boot time using the /etc/sfstab.proto file on the

single system image.

The file systems can be mounted in the background so that the mount operations do not delay the boot

process.

NOTE: You can also use the fstab file to specify which Lustre file systems are to be mounted at boot time.

However, because the fstab file is processed before the sshd daemon is started, you will not be able to

log into the client node to debug any problems that arise during the mount operations.

In addition, the /etc/sfstab file provides additional options that are not available if you use the fstab

file. For example, the /jointfilesconvert/261981/bg option, which specifies that the file system is to be mounted in the background,

cannot be used in the fstab file.

Mount directives in the /etc/sfstab.proto file and the /etc/sfstab file can be specified in any of

the following formats:

lnet://mdsnodes:/mdsname[/profile] mountpoint sfs mountoptions 0 0

http://system_name/filesystem mountpoint sfs mountoptions 0 0

ldap://system_name|serverlist/filesystem mountpoint sfs mountoptions 0 0

See Section 4.2 and Section 4.8 for information on the syntax of the directives, and see Section 4.5 for

details of the mount options that can be used in the /etc/sfstab and /etc/sfstab.proto files.

1 2 ... 62 63 64 65 66 67 68 69 70 71 72 ... 133 134

Pas de commentaire

Red Hat GLOBAL FILE SYSTEM 4.7 Guide de l'utilisateur Page 67