mirror of
https://git.FreeBSD.org/src.git
synced 2024-10-18 02:19:39 +00:00
nfsd.8: Document ways to minimize Copy operation times
For NFSv4.2, a Copy operation can take a long time to complete.
If there is a concurrent ExchangeID or DelegReturn operation
which requires the exclusive lock on all NFSv4 state, this can
result in a stall of the nfsd server.
This patch documents ways to avoid this problem.
This is a content change.
(cherry picked from commit 8f13abb4fd
)
This commit is contained in:
parent
14b2221ae7
commit
23a48a469a
@ -27,7 +27,7 @@
|
||||
.\"
|
||||
.\" @(#)nfsd.8 8.4 (Berkeley) 3/29/95
|
||||
.\"
|
||||
.Dd March 22, 2023
|
||||
.Dd March 16, 2024
|
||||
.Dt NFSD 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -355,3 +355,25 @@ to be set to one on the MDS as a workaround.
|
||||
Linux 5.n kernels appear to have been patched such that this
|
||||
.Xr sysctl 8
|
||||
does not need to be set.
|
||||
.Pp
|
||||
For NFSv4.2, a Copy operation can take a long time to complete.
|
||||
If there is a concurrent ExchangeID or DelegReturn operation
|
||||
which requires the exclusive lock on all NFSv4 state, this can
|
||||
result in a
|
||||
.Dq stall
|
||||
of the
|
||||
.Nm
|
||||
server.
|
||||
If your storage is on ZFS without block cloning enabled,
|
||||
setting the
|
||||
.Xr sysctl 8
|
||||
.Va vfs.zfs.dmu_offset_next_sync
|
||||
to 0 can often avoid this problem.
|
||||
It is also possible to set the
|
||||
.Xr sysctl 8
|
||||
.Va vfs.nfsd.maxcopyrange
|
||||
to 10-100 megabytes to try and reduce Copy operation times.
|
||||
As a last resort, setting
|
||||
.Xr sysctl 8
|
||||
.Va vfs.nfsd.maxcopyrange
|
||||
to 0 disables the Copy operation.
|
||||
|
Loading…
Reference in New Issue
Block a user