From 9d7785b95121218ac879fb2bb54d379bc4ec74df Mon Sep 17 00:00:00 2001 From: rmacklem Date: Wed, 1 Jan 2014 22:22:00 +0000 Subject: [PATCH] MFC: r259089 Document the noncontigwr NFS mount option. This is a content change. git-svn-id: svn://svn.freebsd.org/base/stable/9@260171 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f --- sbin/mount_nfs/mount_nfs.8 | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/sbin/mount_nfs/mount_nfs.8 b/sbin/mount_nfs/mount_nfs.8 index b1b5c6e21..8aaa8d5aa 100644 --- a/sbin/mount_nfs/mount_nfs.8 +++ b/sbin/mount_nfs/mount_nfs.8 @@ -28,7 +28,7 @@ .\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95 .\" $FreeBSD$ .\" -.Dd May 3, 2011 +.Dd December 7, 2013 .Dt MOUNT_NFS 8 .Os .Sh NAME @@ -221,6 +221,19 @@ servers on the client. Note that this option will only be honored when performing the initial mount, it will be silently ignored if used while updating the mount options. +.It Cm noncontigwr +This mount option allows the NFS client to +combine non-contiguous byte ranges being written +such that the dirty byte range becomes a superset of the bytes +that are dirty. +This reduces the number of writes significantly for software +builds. +The merging of byte ranges isn't done if the file has been file +locked, since most applications modifying a file from multiple +clients will use file locking. +As such, this option could result in a corrupted file for the +rare case of an application modifying the file from multiple +clients concurrently without using file locking. .It Cm principal For the RPCSEC_GSS security flavors, such as krb5, krb5i and krb5p, this option sets the name of the host based principal name expected -- 2.45.0