Lines Matching +full:soft +full:- +full:ip
76 .Bd -literal -offset indent
77 jot -w ds 20 0 | xargs mkdir -m 700
99 of these DSs must be mountable via a separate IP address.
103 to create these different IP addresses.
118 .Dq -p
124 .Bd -literal -offset indent
125 nfsv4,minorversion=2,soft,retrans=2
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
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
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
210 .Dq -m
239 .Bd -literal -offset indent
246 Non-pNFS aware clients or NFSv3 mounts will do all I/O RPCs on the MDS,
259 1 - The MDS detects a problem when trying to do proxy
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
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
292 The next step is to clear the IP address in the
297 The command that clears the IP address is
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 {} \;
336 To check that all files have their IP addresses set to 0.0.0.0 these
340 .Bd -literal -offset
341 # cd <top-level-exported-dir>
342 # find . -type f -exec pnfsdsfile {} \; | sed "/nfsv4-data3/!d"
348 .Dq -r
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,
365 but files with the IP address zeroed out on the MDS will not yet use the
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
441 For non-mirrored configurations, all