Lines Matching full:be
15 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
33 servers may be configured to provide a
38 system needs to be configured as a MetaData Server (MDS) and
41 system needs to be configured as one or
46 systems are configured to be NFSv4.1 and NFSv4.2
55 As such, all DS(s) must be upgraded from
61 The DS(s) need to be configured as NFSv4.1 and NFSv4.2 server(s),
64 This directory must be owned by
68 Within this directory there needs to be additional directories named
74 The following command can be run by root when in the top level exported
82 is the default and can be set to a larger value on the MDS as shown below.
84 The top level exported directory used for storage of data files must be
88 It must also be exported to all pNFS aware clients, but these clients do
91 export option and this directory should be exported to them with the same
99 of these DSs must be mountable via a separate IP address.
100 Alias addresses can be set on the DS server system for a network
104 Multiple DSs on the same server may be useful when data for different file systems
109 The MDS must be a separate
123 The DS(s) must all be mounted on the MDS using the following mount options:
128 so that they can be defined as DSs in the
131 Normally these mounts would be entered in the
149 DSs are to be used.
162 This example specifies that the data files should be distributed over the
163 four DSs and File layouts will be issued to pNFS enabled clients.
174 will specify that two way mirroring is to be done, via the
182 will be stored on two of the DSs.
185 It is also possible to specify which DSs are to be used to store data files for
195 will be stored on nfsv4-data0 and nfsv4-data1, whereas the data files for
197 will be store on nfsv4-data2 and nfsv4-data3.
202 This can be used by system administrators to control where data files are
203 stored and might be useful for control of storage use.
204 For this case, it may be convenient to co-locate more than one of the DSs
211 option also needs to be specified.
212 There must be enough DSs assigned to each exported file system on the MDS
214 The above example would be fine for two way mirroring, but four way mirroring
221 This value can be increased from the default of 20, but only when the
225 For a service that will store a large number of files this sysctl should be
235 The clients mounting the MDS must be running the
257 When a mirrored DS fails, it can be disabled one of three ways:
283 Note that the <mounted-on-path-of-DS> must be the exact mounted-on path
296 the data files on this DS will not be used, since they may be out of date.
311 Normally this will be called within a
314 files in the exported directory tree and must be done on the MDS.
321 would be:
337 commands can be used (assuming the
349 to be done again.
350 Once this is done, the replaced/repaired DS can be brought back online.
354 For the nfsv4-data3 example, the command would be:
364 Now, new files can be stored on nfsv4-data3,
373 and it will also normally be used in a
375 For the example case, the commands on the MDS would be:
381 When this completes, the recovery should be complete or at least nearly so.
404 repeatedly, this may be caused by a Read/Write layout that has not
409 All of these commands are designed to be
410 done while the pNFS service is running and can be re-run safely.
437 Since the MDS cannot be mirrored, it is a single point of failure just