[PATCH 0/5] new statd [take 1]

[PATCH 0/5] new statd [take 1]

[Chuck Lever]

Hi Steve-

Here are some man page patches and the one big patch that adds the new
IPv6-capable statd.  I'd like to start socializing these changes to
expedite the new statd into mainline nfs-utils.

---

Chuck Lever (5):
      nfs(5): update nfs(5) with details about IPv6 support
      nfs-utils: introduce new statd implementation
      statd: change default state dir to /var/lib/nfs/statd
      nfs(5): Remove trailing blanks
      nfs(5): Add description of lookupcache mount option


 .gitignore                    |    4 
 Makefile.am                   |    4 
 aclocal/libcap.m4             |   15 +
 aclocal/libsqlite3.m4         |   33 ++
 aclocal/libtirpc.m4           |    2 
 configure.ac                  |   16 +
 utils/Makefile.am             |    7 
 utils/mount/nfs.man           |  377 ++++++++++++------
 utils/new-statd/Makefile.am   |  102 +++++
 utils/new-statd/file.c        |  779 ++++++++++++++++++++++++++++++++++++++
 utils/new-statd/hostname.c    |  520 +++++++++++++++++++++++++
 utils/new-statd/main.c        |  319 ++++++++++++++++
 utils/new-statd/nlmcall.c     |  525 ++++++++++++++++++++++++++
 utils/new-statd/sm-notify.c   |  155 ++++++++
 utils/new-statd/sm-notify.man |  286 ++++++++++++++
 utils/new-statd/sm_inter.x    |  107 +++++
 utils/new-statd/smncall.c     |  774 ++++++++++++++++++++++++++++++++++++++
 utils/new-statd/start-statd   |   12 +
 utils/new-statd/statd.h       |  135 +++++++
 utils/new-statd/statd.man     |  388 +++++++++++++++++++
 utils/new-statd/svc.c         |  841 +++++++++++++++++++++++++++++++++++++++++
 utils/statd/Makefile.am       |    9 
 utils/statd/sm-notify.man     |   12 -
 utils/statd/statd.man         |   10 
 24 files changed, 5282 insertions(+), 150 deletions(-)
 create mode 100644 aclocal/libcap.m4
 create mode 100644 aclocal/libsqlite3.m4
 create mode 100644 utils/new-statd/Makefile.am
 create mode 100644 utils/new-statd/file.c
 create mode 100644 utils/new-statd/hostname.c
 create mode 100644 utils/new-statd/main.c
 create mode 100644 utils/new-statd/nlmcall.c
 create mode 100644 utils/new-statd/sm-notify.c
 create mode 100644 utils/new-statd/sm-notify.man
 create mode 100644 utils/new-statd/sm_inter.x
 create mode 100644 utils/new-statd/smncall.c
 create mode 100644 utils/new-statd/start-statd
 create mode 100644 utils/new-statd/statd.h
 create mode 100644 utils/new-statd/statd.man
 create mode 100644 utils/new-statd/svc.c

-- 
Chuck Lever <chuck.lever@oracle.com>

[PATCH 1/5] nfs(5): Add description of lookupcache mount option

[Chuck Lever]

See kernel commit 7973c1f1.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 utils/mount/nfs.man |   96 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 96 insertions(+), 0 deletions(-)

diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 13de524..87a71c6 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -422,6 +422,49 @@ NFS mount points allowed on a client, but NFS servers must be configured
 to allow clients to connect via non-privileged source ports.
 .IP
 Refer to the SECURITY CONSIDERATIONS section for important details.
+.TP 1.5i
+.BI lookupcache= mode
+Specifies how the kernel manages its cache of directory entries
+for a given mount point.
+.I mode
+can be one of
+.BR all ,
+.BR none ,
+.BR pos ,
+or
+.BR positive .
+This option is supported in kernels 2.6.28 and later.
+.IP
+The Linux NFS client caches the result of all NFS LOOKUP requests.
+If the requested directory entry exists on the server,
+the result is referred to as
+.IR positive .
+If the requested directory entry does not exist on the server,
+the result is referred to as
+.IR negative .
+.IP
+If this option is not specified, or if
+.B all
+is specified, the client assumes both types of directory cache entries
+are valid until their parent directory's cached attributes expire.
+.IP
+If
+.BR pos " or " positive
+is specified, the client assumes positive entries are valid
+until their parent directory's cached attributes expire, but
+always revalidates negative entires before an application
+can use them.
+.IP
+If
+.B none
+is specified,
+the client revalidates both types of directory cache entries
+before an application can use them.
+This permits quick detection of files that were created or removed
+by other clients, but can impact application and server performance.
+.IP
+The DATA AND METADATA COHERENCE section contains a
+detailed discussion of these trade-offs.
 .SS "Valid options for the nfs file system type"
 Use these options, along with the options in the above subsection,
 for mounting the
@@ -1017,6 +1060,59 @@ If absolute cache coherence among clients is required,
 applications should use file locking. Alternatively, applications 
 can also open their files with the O_DIRECT flag
 to disable data caching entirely.
+.SS "Directory entry caching"
+The Linux NFS client caches the result of all NFS LOOKUP requests.
+If the requested directory entry exists on the server,
+the result is referred to as a
+.IR positive " lookup result.
+If the requested directory entry does not exist on the server
+(that is, the server returned ENOENT),
+the result is referred to as
+.IR negative " lookup result.
+.P
+To detect when directory entries have been added or removed
+on the server,
+the Linux NFS client watches a directory's mtime.
+If the client detects a change in a directory's mtime,
+the client drops all cached LOOKUP results for that directory.
+Since the directory's mtime is a cached attribute, it may
+take some time before a client notices it has changed.
+See the descriptions of the
+.BR acdirmin ", " acdirmax ", and " noac
+mount options for more information about
+how long a directory's mtime is cached.
+.P
+Caching directory entries improves the performance of applications that
+do not share files with applications on other clients.
+Using cached information about directories can interfere
+with applications that run concurrently on multiple clients and
+need to detect the creation or removal of files quickly, however.
+The
+.B lookupcache
+mount option allows some tuning of directory entry caching behavior.
+.P
+Before kernel release 2.6.28,
+the Linux NFS client tracked only positive lookup results.
+This permitted applications to detect new directory entries
+created by other clients quickly while still providing some of the
+performance benefits of caching.
+If an application depends on the previous lookup caching behavior
+of the Linux NFS client, you can use
+.BR lookupcache=positive .
+.P
+If the client ignores its cache and validates every application
+lookup request with the server,
+that client can immediately detect when a new directory
+entry has been either created or removed by another client.
+You can specify this behavior using
+.BR lookupcache=none .
+The extra NFS requests needed if the client does not
+cache directory entries can exact a performance penalty.
+Disabling lookup caching
+should result in less of a performance penalty than using
+.BR noac ,
+and has no effect on how the NFS client caches the attributes of files.
+.P
 .SS "The sync mount option"
 The NFS client treats the
 .B sync

[PATCH 2/5] nfs(5): Remove trailing blanks

[Chuck Lever]

Clean up: eliminate trailing blanks in utils/mount/nfs.man.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 utils/mount/nfs.man |  261 +++++++++++++++++++++++++------------------=
--------
 1 files changed, 130 insertions(+), 131 deletions(-)

diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 87a71c6..280ddcb 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -28,7 +28,7 @@ The
 file describes how
 .BR mount (8)
 should assemble a system's file name hierarchy
-from various independent file systems=20
+from various independent file systems
 (including file systems exported by NFS servers).
 Each line in the
 .I /etc/fstab
@@ -56,7 +56,7 @@ by NFS, thus conventionally each contain the digit ze=
ro. For example:
 .P
 The server's hostname and export pathname
 are separated by a colon, while
-the mount options are separated by commas. The remaining fields=20
+the mount options are separated by commas. The remaining fields
 are separated by blanks or tabs.
 The server's hostname can be an unqualified hostname,
 a fully qualified domain name,
@@ -70,17 +70,16 @@ The
 and
 .B nfs4
 file system types share similar mount options,
-which are described below.=20
+which are described below.
 .SH "MOUNT OPTIONS"
-Refer to=20
+Refer to
 .BR mount (8)
 for a description of generic mount options
-available for all file systems. If you do not need to=20
-specify any mount options, use the generic option=20
+available for all file systems. If you do not need to
+specify any mount options, use the generic option
 .B defaults
 in
 .IR /etc/fstab .
-.=20
 .DT
 .SS "Valid options for either the nfs or nfs4 file system type"
 These options are valid to use when mounting either
@@ -100,7 +99,7 @@ option is specified), NFS requests are retried indef=
initely.
 If the
 .B soft
 option is specified, then the NFS client fails an NFS request
-after=20
+after
 .B retrans
 retransmissions have been sent,
 causing the NFS client to return an error
@@ -119,8 +118,8 @@ option may mitigate some of the risks of using the
 option.
 .TP 1.5i
 .BI timeo=3D n
-The time (in tenths of a second) the NFS client waits for a=20
-response before it retries an NFS request. If this=20
+The time (in tenths of a second) the NFS client waits for a
+response before it retries an NFS request. If this
 option is not specified, requests are retried every
 60 seconds for NFS over TCP.
 The NFS client does not perform any kind of timeout backoff
@@ -128,7 +127,7 @@ for NFS over TCP.
 .IP
 However, for NFS over UDP, the client uses an adaptive
 algorithm to estimate an appropriate timeout value for frequently used
-request types (such as READ and WRITE requests), but uses the=20
+request types (such as READ and WRITE requests), but uses the
 .B timeo
 setting for infrequently used request types (such as FSINFO requests).
 If the
@@ -141,13 +140,13 @@ up to a maximum timeout length of 60 seconds.
 .TP 1.5i
 .BI retrans=3D n
 The number of times the NFS client retries a request before
-it attempts further recovery action. If the=20
+it attempts further recovery action. If the
 .B retrans
-option is not specified, the NFS client tries each request=20
+option is not specified, the NFS client tries each request
 three times.
 .IP
 The NFS client generates a "server not responding" message
-after=20
+after
 .B retrans
 retries, then attempts further recovery (depending on whether the
 .B hard
@@ -166,21 +165,21 @@ is 1,048,576 bytes (one megabyte).
 The
 .B rsize
 value is a positive integral multiple of 1024.
-Specified=20
+Specified
 .B rsize
 values lower than 1024 are replaced with 4096; values larger than
 1048576 are replaced with 1048576. If a specified value is within the =
supported
-range but not a multiple of 1024, it is rounded down to the nearest=20
+range but not a multiple of 1024, it is rounded down to the nearest
 multiple of 1024.
 .IP
 If an
 .B rsize
-value is not specified, or if the specified=20
-.B rsize=20
+value is not specified, or if the specified
+.B rsize
 value is larger than the maximum that either client or server can supp=
ort,
 the client and server negotiate the largest
 .B rsize
-value that they can both support.=20
+value that they can both support.
 .IP
 The
 .B rsize
@@ -197,7 +196,7 @@ file.
 .BI wsize=3D n
 The maximum number of bytes per network WRITE request
 that the NFS client can send when writing data to a file
-on an NFS server. The actual data payload size of each=20
+on an NFS server. The actual data payload size of each
 NFS WRITE request is equal to
 or smaller than the
 .B wsize
@@ -207,19 +206,19 @@ is 1,048,576 bytes (one megabyte).
 Similar to
 .B rsize
 , the
-.B wsize=20
+.B wsize
 value is a positive integral multiple of 1024.
-Specified=20
+Specified
 .B wsize
 values lower than 1024 are replaced with 4096; values larger than
 1048576 are replaced with 1048576. If a specified value is within the =
supported
-range but not a multiple of 1024, it is rounded down to the nearest=20
+range but not a multiple of 1024, it is rounded down to the nearest
 multiple of 1024.
 .IP
 If a
 .B wsize
-value is not specified, or if the specified=20
-.B wsize=20
+value is not specified, or if the specified
+.B wsize
 value is larger than the maximum that either client or server can supp=
ort,
 the client and server negotiate the largest
 .B wsize
@@ -235,31 +234,31 @@ file. However, the effective
 .B wsize
 value negotiated by the client and server is reported in the
 .I /proc/mounts
-file.=20
+file.
 .TP 1.5i
 .BR ac " / " noac
-Selects whether the client may cache file attributes. If neither =20
-option is specified (or if=20
+Selects whether the client may cache file attributes. If neither
+option is specified (or if
 .B ac
-is specified), the client caches file =20
-attributes. =20
+is specified), the client caches file
+attributes.
 .IP
-To improve performance, NFS clients cache file =20
-attributes. Every few seconds, an NFS client checks the server's versi=
on of each =20
-file's attributes for updates.  Changes that occur on the server in =20
-those small intervals remain undetected until the client checks the =20
-server again. The=20
+To improve performance, NFS clients cache file
+attributes. Every few seconds, an NFS client checks the server's versi=
on of each
+file's attributes for updates.  Changes that occur on the server in
+those small intervals remain undetected until the client checks the
+server again. The
 .B noac
-option prevents clients from caching file =20
-attributes so that applications can more quickly detect file changes =20
+option prevents clients from caching file
+attributes so that applications can more quickly detect file changes
 on the server.
 .IP
-In addition to preventing the client from caching file attributes, =20
-the=20
+In addition to preventing the client from caching file attributes,
+the
 .B noac
-option forces application writes to become synchronous so =20
-that local changes to a file become visible on the server =20
-immediately.  That way, other clients can quickly detect recent =20
+option forces application writes to become synchronous so
+that local changes to a file become visible on the server
+immediately.  That way, other clients can quickly detect recent
 writes when they check the file's attributes.
 .IP
 Using the
@@ -383,20 +382,20 @@ Refer to the SECURITY CONSIDERATIONS section for =
details.
 .TP 1.5i
 .BR sharecache " / " nosharecache
 Determines how the client's data cache and attribute cache are shared
-when mounting the same export more than once concurrently.  Using the =
=20
-same cache reduces memory requirements on the client and presents =20
-identical file contents to applications when the same remote file is =20
+when mounting the same export more than once concurrently.  Using the
+same cache reduces memory requirements on the client and presents
+identical file contents to applications when the same remote file is
 accessed via different mount points.
 .IP
-If neither option is specified, or if the=20
+If neither option is specified, or if the
 .B sharecache
-option is =20
-specified, then a single cache is used for all mount points that =20
-access the same export.  If the=20
+option is
+specified, then a single cache is used for all mount points that
+access the same export.  If the
 .B nosharecache
-option is specified, =20
-then that mount point gets a unique cache.  Note that when data and =20
-attribute caches are shared, the mount options from the first mount =20
+option is specified,
+then that mount point gets a unique cache.  Note that when data and
+attribute caches are shared, the mount options from the first mount
 point take effect for subsequent concurrent mounts of the same export.
 .IP
 As of kernel 2.6.18, the behavior specified by
@@ -489,9 +488,9 @@ In addition to controlling how the NFS client trans=
mits requests to
 the server, this mount option also controls how the
 .BR mount (8)
 command communicates with the server's rpcbind and mountd services.
-Specifying=20
+Specifying
 .B proto=3Dtcp
-forces all traffic from the=20
+forces all traffic from the
 .BR mount (8)
 command and the NFS client to use TCP.
 Specifying
@@ -617,9 +616,9 @@ It is included for compatibility with other operati=
ng systems.
 .TP 1.5i
 .BR lock " / " nolock
 Selects whether to use the NLM sideband protocol to lock files on the =
server.
-If neither option is specified (or if=20
-.B lock=20
-is specified), NLM locking is used for this mount point.=20
+If neither option is specified (or if
+.B lock
+is specified), NLM locking is used for this mount point.
 When using the
 .B nolock
 option, applications can lock files,
@@ -641,13 +640,13 @@ that do not support the NLM protocol.
 .TP 1.5i
 .BR intr " / " nointr
 Selects whether to allow signals to interrupt file operations
-on this mount point. If neither option=20
-is specified (or if=20
+on this mount point. If neither option
+is specified (or if
 .B nointr
 is specified),
 signals do not interrupt NFS file operations. If
-.B intr=20
-is specified, system calls return EINTR if an in-progress NFS operatio=
n is interrupted by=20
+.B intr
+is specified, system calls return EINTR if an in-progress NFS operatio=
n is interrupted by
 a signal.
 .IP
 Using the
@@ -665,13 +664,13 @@ compatibility with older kernels.
 .TP 1.5i
 .BR cto " / " nocto
 Selects whether to use close-to-open cache coherence semantics.
-If neither option is specified (or if=20
+If neither option is specified (or if
 .B cto
 is specified), the client uses close-to-open
-cache coherence semantics. If the=20
-.B nocto=20
+cache coherence semantics. If the
+.B nocto
 option is specified, the client uses a non-standard heuristic to deter=
mine when
-files on the server have changed.=20
+files on the server have changed.
 .IP
 Using the
 .B nocto
@@ -683,13 +682,13 @@ of this option in more detail.
 .BR acl " / " noacl
 Selects whether to use the NFSACL sideband protocol on this mount poin=
t.
 The NFSACL sideband protocol is a proprietary protocol
-implemented in Solaris that manages Access Control Lists. NFSACL was n=
ever=20
+implemented in Solaris that manages Access Control Lists. NFSACL was n=
ever
 made a standard part of the NFS protocol specification.
 .IP
-If neither=20
+If neither
 .B acl
-nor=20
-.B noacl=20
+nor
+.B noacl
 option is specified,
 the NFS client negotiates with the server
 to see if the NFSACL protocol is supported,
@@ -703,7 +702,7 @@ Selects whether to use NFS version 3 READDIRPLUS re=
quests.
 If this option is not specified, the NFS client uses READDIRPLUS reque=
sts
 on NFS version 3 mounts to read small directories.
 Some applications perform better if the client uses only READDIR reque=
sts
-for all directories. =20
+for all directories.
 .SS "Valid options for the nfs4 file system type"
 Use these options, along with the options in the first subsection abov=
e,
 for mounting the
@@ -719,8 +718,8 @@ can be either
 or
 .BR tcp .
 All NFS version 4 servers are required to support TCP,
-so if this mount option is not specified, the NFS version 4 client=20
-uses the TCP transport protocol.=20
+so if this mount option is not specified, the NFS version 4 client
+uses the TCP transport protocol.
 Refer to the TRANSPORT METHODS section for more details.
 .TP 1.5i
 .BI port=3D n
@@ -743,12 +742,12 @@ or the server's NFS service is not available on t=
he advertised port.
 .TP 1.5i
 .BR intr " / " nointr
 Selects whether to allow signals to interrupt file operations
-on this mount point. If neither option is specified (or if=20
-.B intr=20
-is specified), system calls return EINTR if an in-progress NFS operati=
on =20
-is interrupted by a signal.  If=20
+on this mount point. If neither option is specified (or if
+.B intr
+is specified), system calls return EINTR if an in-progress NFS operati=
on
+is interrupted by a signal.  If
 .B nointr
-is specified, signals do not =20
+is specified, signals do not
 interrupt NFS operations.
 .IP
 Using the
@@ -770,7 +769,7 @@ for NFS directories on this mount point.
 If neither
 .B cto
 nor
-.B nocto=20
+.B nocto
 is specified,
 the default is to use close-to-open cache coherence
 semantics for directories.
@@ -780,11 +779,11 @@ The DATA AND METADATA COHERENCE section discusses
 the behavior of this option in more detail.
 .TP 1.5i
 .BI clientaddr=3D n.n.n.n
-Specifies  a  single  IPv4  address  (in dotted-quad form)=20
-that the NFS client advertises to allow servers=20
-to perform NFS version 4 callback requests against=20
-files on this mount point. If  the  server is unable to=20
-establish callback connections to clients, performance=20
+Specifies  a  single  IPv4  address  (in dotted-quad form)
+that the NFS client advertises to allow servers
+to perform NFS version 4 callback requests against
+files on this mount point. If  the  server is unable to
+establish callback connections to clients, performance
 may degrade, or accesses to files may temporarily hang.
 .IP
 If this option is not specified, the
@@ -794,7 +793,7 @@ The automatic discovery process is not perfect, how=
ever.
 In the presence of multiple client network interfaces,
 special routing policies,
 or atypical network topologies,
-the exact address to use for callbacks may be nontrivial to determine.=
=20
+the exact address to use for callbacks may be nontrivial to determine.
 .SH EXAMPLES
 To mount an export using NFS version 2,
 use the
@@ -867,33 +866,33 @@ and data transfer size settings for a mount point=
=2E
 In some cases, however, it pays to specify
 these settings explicitly using mount options.
 .P
-Traditionally, NFS clients used the UDP transport exclusively for =20
-transmitting requests to servers.  Though its implementation is =20
-simple, NFS over UDP has many limitations that prevent smooth =20
-operation and good performance in some common deployment =20
-environments.  Even an insignificant packet loss rate results in the =20
-loss of whole NFS requests; as such, retransmit timeouts are usually =20
-in the subsecond range to allow clients to recover quickly from =20
-dropped requests, but this can result in extraneous network traffic =20
+Traditionally, NFS clients used the UDP transport exclusively for
+transmitting requests to servers.  Though its implementation is
+simple, NFS over UDP has many limitations that prevent smooth
+operation and good performance in some common deployment
+environments.  Even an insignificant packet loss rate results in the
+loss of whole NFS requests; as such, retransmit timeouts are usually
+in the subsecond range to allow clients to recover quickly from
+dropped requests, but this can result in extraneous network traffic
 and server load.
 .P
-However, UDP can be quite effective in specialized settings where =20
-the network=E2=80=99s MTU is large relative to NFS=E2=80=99s data tran=
sfer size (such =20
-as network environments that enable jumbo Ethernet frames).  In such =20
-environments, trimming the=20
-.B rsize=20
-and=20
-.B wsize=20
-settings so that each =20
-NFS read or write request fits in just a few network frames (or even =20
-in  a single  frame) is advised.  This reduces the probability that =20
-the loss of a single MTU-sized network frame results in the loss of =20
+However, UDP can be quite effective in specialized settings where
+the network=E2=80=99s MTU is large relative to NFS=E2=80=99s data tran=
sfer size (such
+as network environments that enable jumbo Ethernet frames).  In such
+environments, trimming the
+.B rsize
+and
+.B wsize
+settings so that each
+NFS read or write request fits in just a few network frames (or even
+in  a single  frame) is advised.  This reduces the probability that
+the loss of a single MTU-sized network frame results in the loss of
 an entire large read or write request.
 .P
-TCP is the default transport protocol used for all modern NFS=20
+TCP is the default transport protocol used for all modern NFS
 implementations.  It performs well in almost every conceivable
-network environment and provides excellent guarantees against data=20
-corruption caused by network unreliability.  TCP is often a =20
+network environment and provides excellent guarantees against data
+corruption caused by network unreliability.  TCP is often a
 requirement for mounting a server through a network firewall.
 .P
 Under normal circumstances, networks drop packets much more
@@ -904,11 +903,11 @@ After  the client exhausts its retransmits (the v=
alue of the
 .B retrans
 mount option), it assumes a network partition has occurred,
 and attempts to reconnect to the server on a fresh socket. Since
-TCP itself makes network data transfer reliable,=20
+TCP itself makes network data transfer reliable,
 .B rsize
-and=20
+and
 .B wsize
-can safely be allowed to default to the largest values supported by =20
+can safely be allowed to default to the largest values supported by
 both client and server, independent of the network's MTU size.
 .SS "Using the mountproto mount option"
 This section applies only to NFS version 2 and version 3 mounts
@@ -993,8 +992,8 @@ Some modern cluster file systems provide
 perfect cache coherence among their clients.
 Perfect cache coherence among disparate NFS clients
 is expensive to achieve, especially on wide area networks.
-As such, NFS settles for weaker cache coherence that=20
-satisfies the requirements of most file sharing types. Normally,=20
+As such, NFS settles for weaker cache coherence that
+satisfies the requirements of most file sharing types. Normally,
 file sharing is completely sequential:
 first client A opens a file, writes something to it, then closes it;
 then client B opens the same file, and reads the changes.
@@ -1028,7 +1027,7 @@ it is still difficult to tell whether it was
 that client's updates or some other client's updates
 that altered the file.
 .SS "Attribute caching"
-Use the=20
+Use the
 .B noac
 mount option to achieve attribute cache coherence
 among multiple clients.
@@ -1057,7 +1056,7 @@ The NFS protocol is not designed to support
 true cluster file system cache coherence
 without some type of application serialization.
 If absolute cache coherence among clients is required,
-applications should use file locking. Alternatively, applications=20
+applications should use file locking. Alternatively, applications
 can also open their files with the O_DIRECT flag
 to disable data caching entirely.
 .SS "Directory entry caching"
@@ -1117,7 +1116,7 @@ and has no effect on how the NFS client caches th=
e attributes of files.
 The NFS client treats the
 .B sync
 mount option differently than some other file systems
-(refer to=20
+(refer to
 .BR mount (8)
 for a description of the generic
 .B sync
@@ -1128,16 +1127,16 @@ If neither
 .B sync
 nor
 .B async
-is specified (or if the=20
-.B async=20
+is specified (or if the
+.B async
 option is specified),
 the NFS client delays sending application
 writes to the server
-until any of these events occur:=20
+until any of these events occur:
 .IP
 Memory pressure forces reclamation of system memory resources.
 .IP
-An application flushes file data explicitly with=20
+An application flushes file data explicitly with
 .BR sync (2),
 .BR msync (2),
 or
@@ -1165,7 +1164,7 @@ but at a significant performance cost.
 Applications can use the O_SYNC open flag to force application
 writes to individual files to go to the server immediately without
 the use of the
-.B sync=20
+.B sync
 mount option.
 .SS "Using file locks with NFS"
 The Network Lock Manager protocol is a separate sideband protocol
@@ -1200,15 +1199,15 @@ mount option. NLM locking must be disabled with=
 the
 .B nolock
 option when using NFS to mount
 .I /var
-because=20
-.I /var=20
+because
+.I /var
 contains files used by the NLM implementation on Linux.
 .P
 Specifying the
 .B nolock
 option may also be advised to improve the performance
 of a proprietary application which runs on a single client
-and uses file locks extensively.=20
+and uses file locks extensively.
 .SS "NFS version 4 caching features"
 The data and metadata caching behavior of NFS version 4
 clients is similar to that of earlier versions.
@@ -1292,7 +1291,7 @@ authentication, and in-transit data protection.
 The NFS version 4 specification mandates NFSv4 ACLs,
 RPCGSS authentication, and RPCGSS security flavors
 that provide per-RPC integrity checking and encryption.
-Because NFS version 4 combines the =20
+Because NFS version 4 combines the
 function of the sideband protocols into the main NFS protocol,
 the new security features apply to all NFS version 4 operations
 including mounting, file locking, and so on.
@@ -1306,11 +1305,11 @@ that is in effect on a given NFS mount point.
 Specifying
 .B sec=3Dkrb5
 provides cryptographic proof of a user's identity in each RPC request.
-This provides strong verification of the identity of users=20
+This provides strong verification of the identity of users
 accessing data on the server.
 Note that additional configuration besides adding this mount option
 is required in order to enable Kerberos security.
-Refer to the=20
+Refer to the
 .BR rpc.gssd (8)
 man page for details.
 .P
@@ -1395,15 +1394,15 @@ filter rules.
 It is still possible to mount an NFS server through a firewall,
 though some of the
 .BR mount (8)
-command's automatic service endpoint discovery mechanisms may not work=
; this=20
+command's automatic service endpoint discovery mechanisms may not work=
; this
 requires you to provide specific endpoint details via NFS mount option=
s.
 .P
 NFS servers normally run a portmapper or rpcbind daemon to advertise
-their service endpoints to clients. Clients use the rpcbind daemon to =
determine:=20
+their service endpoints to clients. Clients use the rpcbind daemon to =
determine:
 .IP
 What network port each RPC-based service is using
 .IP
-What transport protocols each RPC-based service supports=20
+What transport protocols each RPC-based service supports
 .P
 The rpcbind daemon uses a well-known port number (111) to help clients=
 find a service endpoint.
 Although NFS often uses a standard port number (2049),
@@ -1435,9 +1434,9 @@ of the NFS version 3 specification, however.
 .P
 The NFS version 4 specification mandates a new version
 of Access Control Lists that are semantically richer than POSIX ACLs.
-NFS version 4 ACLs are not fully compatible with POSIX ACLs; as such,=20
+NFS version 4 ACLs are not fully compatible with POSIX ACLs; as such,
 some translation between the two is required
-in an environment that mixes POSIX ACLs and NFS version 4.=20
+in an environment that mixes POSIX ACLs and NFS version 4.
 .SH FILES
 .TP 1.5i
 .I /etc/fstab
@@ -1514,4 +1513,4 @@ RFC 1833 for the RPC bind specification.
 .br
 RFC 2203 for the RPCSEC GSS API protocol specification.
 .br
-RFC 3530 for the NFS version 4 specification.=20
+RFC 3530 for the NFS version 4 specification.

[PATCH 3/5] statd: change default state dir to /var/lib/nfs/statd

[Chuck Lever]

rpc.statd and friends drop root privileges when they start up.  They
set their effective UID and GID to the owner and group of the statd
state directory, which is by default /var/lib/nfs.

This directory contains a number of other objects, however, and is
usually owned by root:root.  This means if distributions aren't
careful about how nfs-utils is built, their statd will run as root
despite dropping privileges.

So change the default behavior to what Red Hat does: use a separate
subdirectory (/var/lib/nfs/statd) that can have unique ownership,
just for the state directory.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 configure.ac              |    4 ++--
 utils/statd/sm-notify.man |   12 ++++++------
 utils/statd/statd.man     |   10 +++++-----
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/configure.ac b/configure.ac
index e0ca70e..2b1994d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -18,9 +18,9 @@ AC_ARG_WITH(release,
 	RELEASE=1)
 	AC_SUBST(RELEASE)
 AC_ARG_WITH(statedir,
-	[  --with-statedir=/foo    use state dir /foo [/var/lib/nfs]],
+	[  --with-statedir=/foo    use state dir /foo [/var/lib/nfs/statd]],
 	statedir=$withval,
-	statedir=/var/lib/nfs)
+	statedir=/var/lib/nfs/statd)
 	AC_SUBST(statedir)
 AC_ARG_WITH(statduser,
 	[AC_HELP_STRING([--with-statduser=rpcuser],
diff --git a/utils/statd/sm-notify.man b/utils/statd/sm-notify.man
index dd03b8d..69b7059 100644
--- a/utils/statd/sm-notify.man
+++ b/utils/statd/sm-notify.man
@@ -33,7 +33,7 @@ but this is configurable.
 For each NFS client or server machine to be monitored,
 .B rpc.statd
 creates a file in
-.BR /var/lib/nfs/sm ", "
+.BR /var/lib/nfs/statd/sm ", "
 and removes the file if monitoring is no longer required.
 .PP
 When the machine is rebooted,
@@ -47,7 +47,7 @@ Each machine has an
 which is basically an integer counter that is incremented
 each time the machine reboots. This counter is stored
 in
-.BR /var/lib/nfs/state ,
+.BR /var/lib/nfs/statd/state ,
 and updated by
 .BR sm-notify .
 .SS Security
@@ -149,13 +149,13 @@ By default,
 .B sm-notify
 forks and puts itself in the background after obtaining the
 list of hosts from
-.BR /var/lib/nfs/sm .
+.BR /var/lib/nfs/statd/sm .
 .SH FILES
-.BR /var/lib/nfs/state
+.BR /var/lib/nfs/statd/state
 .br
-.BR /var/lib/nfs/sm/*
+.BR /var/lib/nfs/statd/sm/*
 .br
-.BR /var/lib/nfs/sm.bak/*
+.BR /var/lib/nfs/statd/sm.bak/*
 .br
 .BR /var/run/sm-notify.pid
 .SH SEE ALSO
diff --git a/utils/statd/statd.man b/utils/statd/statd.man
index e8be9f3..4ed186e 100644
--- a/utils/statd/statd.man
+++ b/utils/statd/statd.man
@@ -24,7 +24,7 @@ reboots.
 For each NFS client or server machine to be monitored,
 .B rpc.statd
 creates a file in
-.BR /var/lib/nfs/sm .
+.BR /var/lib/nfs/statd/sm .
 When starting, it normally runs
 .B sm-notify
 to iterate through these files and notify the
@@ -95,7 +95,7 @@ a port may be useful when implementing a firewall.
 .BI "\-P," "" " \-\-state\-directory\-path "  directory
 specify a directory in which to place statd state information.
 If this option is not specified the default of 
-.BR /var/lib/nfs
+.BR /var/lib/nfs/statd
 is used.
 .TP
 .B -N
@@ -176,11 +176,11 @@ and send notifications to clients. This can be used in High Availability NFS
 of an NFS export from another server.
 
 .SH FILES
-.BR /var/lib/nfs/state
+.BR /var/lib/nfs/statd/state
 .br
-.BR /var/lib/nfs/sm/*
+.BR /var/lib/nfs/statd/sm/*
 .br
-.BR /var/lib/nfs/sm.bak/*
+.BR /var/lib/nfs/statd/sm.bak/*
 .SH SEE ALSO
 .BR rpc.nfsd(8),
 .BR portmap(8)

[PATCH 5/5] NFS man page: update nfs(5) with details about IPv6 support

[Chuck Lever]

Add details to nfs(5) about how to specify raw IPv6 addresses when mounting an
NFS server.  Mounting via an IPv6 NFS server via hostname should work as it
does with IPv4.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---

 utils/mount/nfs.man |   22 ++++++++++++++++++++--
 1 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 280ddcb..e543fe4 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -58,9 +58,17 @@ The server's hostname and export pathname
 are separated by a colon, while
 the mount options are separated by commas. The remaining fields
 are separated by blanks or tabs.
+.P
 The server's hostname can be an unqualified hostname,
 a fully qualified domain name,
-or a dotted quad IPv4 address.
+a dotted quad IPv4 address, or
+an IPv6 address enclosed in square brackets.
+Link-local and site-local IPv6 addresses must be accompanied by an
+interface identifier.
+See
+.BR ipv6 (7)
+for details on specifying raw IPv6 addresses.
+.P
 The
 .I fstype
 field contains either "nfs" (for version 2 or version 3 NFS mounts)
@@ -779,7 +787,8 @@ The DATA AND METADATA COHERENCE section discusses
 the behavior of this option in more detail.
 .TP 1.5i
 .BI clientaddr= n.n.n.n
-Specifies  a  single  IPv4  address  (in dotted-quad form)
+Specifies a single IPv4 address (in dotted-quad form),
+or a non-link-local IPv6 address,
 that the NFS client advertises to allow servers
 to perform NFS version 4 callback requests against
 files on this mount point. If  the  server is unable to
@@ -848,6 +857,14 @@ This example can be used to mount /usr over NFS.
 .TA 2.5i +0.7i +0.7i +.7i
 	server:/export	/usr	nfs	ro,nolock,nocto,actimeo=3600	0 0
 .FI
+.P
+This example shows how to mount an NFS server
+using a raw IPv6 link-local address.
+.P
+.NF
+.TA 2.5i +0.7i +0.7i +.7i
+	[fe80::215:c5ff:fb3e:e2b1%eth0]:/export	/mnt	nfs	defaults	0 0
+.FI
 .SH "TRANSPORT METHODS"
 NFS clients send requests to NFS servers via
 Remote Procedure Calls, or
@@ -1491,6 +1508,7 @@ such as security negotiation, server referrals, and named attributes.
 .BR mount.nfs (5),
 .BR umount.nfs (5),
 .BR exports (5),
+.BR ipv6 (7),
 .BR nfsd (8),
 .BR sm-notify (8),
 .BR rpc.statd (8),

Re: [PATCH 0/5] new statd [take 1]

[Chuck Lever]

The big patch didn't make it through the mailing list, apparently.  I  
didn't receive any kind of bounce message.

Does anyone know who moderates this list and if there is a size limit?


On Aug 4, 2009, at 2:06 PM, Chuck Lever wrote:

> Hi Steve-
>
> Here are some man page patches and the one big patch that adds the new
> IPv6-capable statd.  I'd like to start socializing these changes to
> expedite the new statd into mainline nfs-utils.
>
> ---
>
> Chuck Lever (5):
>      nfs(5): update nfs(5) with details about IPv6 support
>      nfs-utils: introduce new statd implementation
>      statd: change default state dir to /var/lib/nfs/statd
>      nfs(5): Remove trailing blanks
>      nfs(5): Add description of lookupcache mount option
>
>
> .gitignore                    |    4
> Makefile.am                   |    4
> aclocal/libcap.m4             |   15 +
> aclocal/libsqlite3.m4         |   33 ++
> aclocal/libtirpc.m4           |    2
> configure.ac                  |   16 +
> utils/Makefile.am             |    7
> utils/mount/nfs.man           |  377 ++++++++++++------
> utils/new-statd/Makefile.am   |  102 +++++
> utils/new-statd/file.c        |  779 ++++++++++++++++++++++++++++++++ 
> ++++++
> utils/new-statd/hostname.c    |  520 +++++++++++++++++++++++++
> utils/new-statd/main.c        |  319 ++++++++++++++++
> utils/new-statd/nlmcall.c     |  525 ++++++++++++++++++++++++++
> utils/new-statd/sm-notify.c   |  155 ++++++++
> utils/new-statd/sm-notify.man |  286 ++++++++++++++
> utils/new-statd/sm_inter.x    |  107 +++++
> utils/new-statd/smncall.c     |  774 ++++++++++++++++++++++++++++++++ 
> ++++++
> utils/new-statd/start-statd   |   12 +
> utils/new-statd/statd.h       |  135 +++++++
> utils/new-statd/statd.man     |  388 +++++++++++++++++++
> utils/new-statd/svc.c         |  841 ++++++++++++++++++++++++++++++++ 
> +++++++++
> utils/statd/Makefile.am       |    9
> utils/statd/sm-notify.man     |   12 -
> utils/statd/statd.man         |   10
> 24 files changed, 5282 insertions(+), 150 deletions(-)
> create mode 100644 aclocal/libcap.m4
> create mode 100644 aclocal/libsqlite3.m4
> create mode 100644 utils/new-statd/Makefile.am
> create mode 100644 utils/new-statd/file.c
> create mode 100644 utils/new-statd/hostname.c
> create mode 100644 utils/new-statd/main.c
> create mode 100644 utils/new-statd/nlmcall.c
> create mode 100644 utils/new-statd/sm-notify.c
> create mode 100644 utils/new-statd/sm-notify.man
> create mode 100644 utils/new-statd/sm_inter.x
> create mode 100644 utils/new-statd/smncall.c
> create mode 100644 utils/new-statd/start-statd
> create mode 100644 utils/new-statd/statd.h
> create mode 100644 utils/new-statd/statd.man
> create mode 100644 utils/new-statd/svc.c
>
> -- 
> Chuck Lever <chuck.lever@oracle.com>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs"  
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Chuck Lever
chuck[dot]lever[at]oracle[dot]com

Re: [PATCH 0/5] new statd [take 1]

[J. Bruce Fields]

On Wed, Aug 05, 2009 at 09:51:05AM -0400, Chuck Lever wrote:
> The big patch didn't make it through the mailing list, apparently.  I  
> didn't receive any kind of bounce message.
>
> Does anyone know who moderates this list and if there is a size limit?

I've had good luck with email to postmaster@vger.kernel.org for help
with this kind of problem in the past.

--b.

>
>
> On Aug 4, 2009, at 2:06 PM, Chuck Lever wrote:
>
>> Hi Steve-
>>
>> Here are some man page patches and the one big patch that adds the new
>> IPv6-capable statd.  I'd like to start socializing these changes to
>> expedite the new statd into mainline nfs-utils.
>>
>> ---
>>
>> Chuck Lever (5):
>>      nfs(5): update nfs(5) with details about IPv6 support
>>      nfs-utils: introduce new statd implementation
>>      statd: change default state dir to /var/lib/nfs/statd
>>      nfs(5): Remove trailing blanks
>>      nfs(5): Add description of lookupcache mount option
>>
>>
>> .gitignore                    |    4
>> Makefile.am                   |    4
>> aclocal/libcap.m4             |   15 +
>> aclocal/libsqlite3.m4         |   33 ++
>> aclocal/libtirpc.m4           |    2
>> configure.ac                  |   16 +
>> utils/Makefile.am             |    7
>> utils/mount/nfs.man           |  377 ++++++++++++------
>> utils/new-statd/Makefile.am   |  102 +++++
>> utils/new-statd/file.c        |  779 ++++++++++++++++++++++++++++++++ 
>> ++++++
>> utils/new-statd/hostname.c    |  520 +++++++++++++++++++++++++
>> utils/new-statd/main.c        |  319 ++++++++++++++++
>> utils/new-statd/nlmcall.c     |  525 ++++++++++++++++++++++++++
>> utils/new-statd/sm-notify.c   |  155 ++++++++
>> utils/new-statd/sm-notify.man |  286 ++++++++++++++
>> utils/new-statd/sm_inter.x    |  107 +++++
>> utils/new-statd/smncall.c     |  774 ++++++++++++++++++++++++++++++++ 
>> ++++++
>> utils/new-statd/start-statd   |   12 +
>> utils/new-statd/statd.h       |  135 +++++++
>> utils/new-statd/statd.man     |  388 +++++++++++++++++++
>> utils/new-statd/svc.c         |  841 ++++++++++++++++++++++++++++++++ 
>> +++++++++
>> utils/statd/Makefile.am       |    9
>> utils/statd/sm-notify.man     |   12 -
>> utils/statd/statd.man         |   10
>> 24 files changed, 5282 insertions(+), 150 deletions(-)
>> create mode 100644 aclocal/libcap.m4
>> create mode 100644 aclocal/libsqlite3.m4
>> create mode 100644 utils/new-statd/Makefile.am
>> create mode 100644 utils/new-statd/file.c
>> create mode 100644 utils/new-statd/hostname.c
>> create mode 100644 utils/new-statd/main.c
>> create mode 100644 utils/new-statd/nlmcall.c
>> create mode 100644 utils/new-statd/sm-notify.c
>> create mode 100644 utils/new-statd/sm-notify.man
>> create mode 100644 utils/new-statd/sm_inter.x
>> create mode 100644 utils/new-statd/smncall.c
>> create mode 100644 utils/new-statd/start-statd
>> create mode 100644 utils/new-statd/statd.h
>> create mode 100644 utils/new-statd/statd.man
>> create mode 100644 utils/new-statd/svc.c
>>
>> -- 
>> Chuck Lever <chuck.lever@oracle.com>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs"  
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> -- 
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 0/5] new statd [take 1]

[Steve Dickson]

On 08/04/2009 02:06 PM, Chuck Lever wrote:
> Hi Steve-
> 
> Here are some man page patches and the one big patch that adds the new
> IPv6-capable statd.  I'd like to start socializing these changes to
> expedite the new statd into mainline nfs-utils.
> 
> ---
> 
> Chuck Lever (5):
>       nfs(5): update nfs(5) with details about IPv6 support
>       nfs-utils: introduce new statd implementation
I 'm waited on these to allow the new statd implementation to shake
out a bit port... 

>       statd: change default state dir to /var/lib/nfs/statd
I would like to get an 'ACK' from other distros on this one since
they could depending on what happens today...  

>       nfs(5): Remove trailing blanks
>       nfs(5): Add description of lookupcache mount option
I committed these

steved.

Re: [PATCH 0/5] new statd [take 1]

[Chuck Lever]

On Aug 16, 2009, at 4:35 PM, Steve Dickson wrote:
> On 08/04/2009 02:06 PM, Chuck Lever wrote:
>> Hi Steve-
>>
>> Here are some man page patches and the one big patch that adds the  
>> new
>> IPv6-capable statd.  I'd like to start socializing these changes to
>> expedite the new statd into mainline nfs-utils.
>>
>> ---
>>
>> Chuck Lever (5):
>>      nfs(5): update nfs(5) with details about IPv6 support
>>      nfs-utils: introduce new statd implementation
> I 'm waited on these to allow the new statd implementation to shake
> out a bit port...
>
>>      statd: change default state dir to /var/lib/nfs/statd
> I would like to get an 'ACK' from other distros on this one since
> they could depending on what happens today...

This one was purposely dropped in the second round of patches, not to  
be resubmitted.  You can ignore it.

>>      nfs(5): Remove trailing blanks
>>      nfs(5): Add description of lookupcache mount option
> I committed these


OK.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com