Lines Matching +full:conf +full:- +full:ds
42 more Data Servers (DS)s.
52 All DS(s) and the MDS should support NFSv4.2 as well as NFSv4.1.
53 Mixing an MDS that supports NFSv4.2 with any DS(s) that do not support
55 As such, all DS(s) must be upgraded from
60 .Sh DS server configuration
61 The DS(s) need to be configured as NFSv4.1 and NFSv4.2 server(s),
76 .Bd -literal -offset indent
77 jot -w ds 20 0 | xargs mkdir -m 700
100 Alias addresses can be set on the DS server system for a network
118 .Dq -p
123 The DS(s) must all be mounted on the MDS using the following mount options:
124 .Bd -literal -offset indent
129 .Dq -p
134 For example, if there are four DSs named nfsv4-data[0-3], the
137 .Bd -literal -offset
138 nfsv4-data0:/ /data0 nfs rw,nfsv4,minorversion=2,soft,retrans=2 0 0
139 nfsv4-data1:/ /data1 nfs rw,nfsv4,minorversion=2,soft,retrans=2 0 0
140 nfsv4-data2:/ /data2 nfs rw,nfsv4,minorversion=2,soft,retrans=2 0 0
141 nfsv4-data3:/ /data3 nfs rw,nfsv4,minorversion=2,soft,retrans=2 0 0
147 .Dq -p
156 .Xr rc.conf 5
158 .Bd -literal -offset
159 nfs_server_flags="-u -t -n 128 -p nfsv4-data0:/data0,nfsv4-data1:/data1,nfsv4-data2:/data2,nfsv4-da…
166 non-zero in your
167 .Xr sysctl.conf 5
175 .Dq -m
177 .Bd -literal -offset
178 nfs_server_flags="-u -t -n 128 -p nfsv4-data0:/data0,nfsv4-data1:/data1,nfsv4-data2:/data2,nfsv4-da…
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.
198 .Bd -literal -offset
199 nfs_server_flags="-u -t -n 128 -p nfsv4-data0:/data0#/export1,nfsv4-data1:/data1#/export1,nfsv4-dat…
204 For this case, it may be convenient to co-locate more than one of the DSs
207 server, using separate file systems on the DS system
208 for storage of the respective DS's data files.
210 .Dq -m
218 The number of subdirectories in each DS is defined by the
239 .Bd -literal -offset indent
244 .Xr rc.conf 5
246 Non-pNFS aware clients or NFSv3 mounts will do all I/O RPCs on the MDS,
247 which acts as a proxy for the appropriate DS(s).
257 When a mirrored DS fails, it can be disabled one of three ways:
259 1 - The MDS detects a problem when trying to do proxy
260 operations on the DS.
262 after the DS failure or network partitioning occurs.
264 2 - A pNFS client can report an I/O error that occurred for a DS to the MDS in
267 3 - The system administrator can perform the pnfsdskill(8) command on the MDS
270 (Device not configured) that normally means the DS was already
273 there is a problem with a mirrored DS, doing the command is recommended.
275 Once a system administrator knows that a mirrored DS has malfunctioned
278 .Bd -literal -offset indent
279 # pnfsdskill <mounted-on-path-of-DS>
280 # umount -N <mounted-on-path-of-DS>
283 Note that the <mounted-on-path-of-DS> must be the exact mounted-on path
284 string used when the DS was mounted on the MDS.
286 Once the mirrored DS has been disabled, the pNFS service should continue to
287 function, but file updates will only happen on the DS(s) that have not been disabled.
288 Assuming two way mirroring, that implies the one DS of the pair stored in the
290 extended attribute for the file on the MDS, for files stored on the disabled DS.
294 extended attribute on all files on the MDS for the failed DS.
295 This is done so that, when the disabled DS is repaired and brought back online,
296 the data files on this DS will not be used, since they may be out of date.
300 .Dq -r
302 .Bd -literal -offset
304 # pnfsdsfile -r nfsv4-data3 yyy.c
305 yyy.c: nfsv4-data2.home.rick ds0/207508569ff983350c000000ec7c0200e4c57b2e0000000000000000 0.0.0.0 d…
308 replaces nfsv4-data3 with an IPv4 address of 0.0.0.0, so that nfsv4-data3
318 .Dq -q
320 If the disabled/repaired DS is nfsv4-data3, the commands done on the MDS
322 .Bd -literal -offset
323 # cd <top-level-exported-dir>
324 # find . -type f -exec pnfsdsfile -q -r nfsv4-data3 {} \;
340 .Bd -literal -offset
341 # cd <top-level-exported-dir>
342 # find . -type f -exec pnfsdsfile {} \; | sed "/nfsv4-data3/!d"
348 .Dq -r
350 Once this is done, the replaced/repaired DS can be brought back online.
354 For the nfsv4-data3 example, the command would be:
355 .Bd -literal -offset
356 # mount -t nfs -o nfsv4,minorversion=2,soft,retrans=2 nfsv4-data3:/ /data3
359 Then restart the nfsd to re-enable the DS.
360 .Bd -literal -offset
364 Now, new files can be stored on nfsv4-data3,
366 repaired DS (nfsv4-data3).
370 data to the repaired DS and re-enable use of this mirror for it.
376 .Bd -literal -offset
377 # cd <top-level-exported-dir>
378 # find . -type f -exec pnfsdscopymr -r /data3 {} \;
387 .Bd -literal -offset
388 # cd <top-level-exported-dir>
389 # find . -type f -exec pnfsdsfile {} \; | sed "/0\.0\.0\.0/!d"
396 .Bd -literal -offset
397 # pnfsdscopymr -r /data3 <file-path-reported>
410 done while the pNFS service is running and can be re-run safely.
414 .Bd -literal -offset indent
415 https://people.freebsd.org/~rmacklem/pnfs-planb-setup.txt
423 .Xr rc.conf 5 ,
424 .Xr sysctl.conf 5 ,
441 For non-mirrored configurations, all