anchor.diff:  
   #### File Locking with `flock()` and `lockf()`/`fcntl()`
   
  -Apps that use file locking through unix system calls such as `flock()` and `fcntl()` or script commands such as `flock` should use the `nfs-experimental` service.  The `nfs` service uses a fuse mounting process that does not enforce locks across Diego cells.
  +Apps that use file locking through unix system calls such as `flock()` and `fcntl()` or script commands such as `flock` may use the `nfs` service.  The `nfs-legacy` service uses a fuse mounting process that does not enforce locks across Diego cells.
  
positive.code: You can run the `cf services` command to confirm that your newly-created NFS volume service displays in the output.
  
  
  #### Create with `nfs-experimental` Service:
  
  You can create a NFS volume service with NFSv3 or NFSv4 using the `Existing` plan of the `nfs-experimental` service. Run the following command:
  
  ```
  $ cf create-service nfs-experimental Existing SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "version":"NFS-PROTOCOL"}'
  ```
  
  Where:
  
  * `SERVICE-INSTANCE-NAME` is a name you provide for this NFS volume service instance.
  * `SERVER/SHARE` is the NFS address of your server and share.
  * `VERSION` is the NFS protocol you want to use. For example, if you want to use NFSv4, set the version to `4.1`.
  
  <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  
negative.code: 
  Cloud Foundry offers two NFS volume services:
  
  * `nfs`: This volume service provides support for both NFSv3 (default) and NFSv4 volumes.
    * For NFSv4,  specify a `version` parameter in the create configuration.
    * For read-only mounts, the driver enables attribute caching. This results in fewer attribute RPCs and better performance.
    * When you omit `uid` and `gid` or `username` and `password` in bind configuration, the driver skips `mapfs` mounting and performs just the normal kernel mount of the NFS file system without the overhead associated with FUSE mounts.
  * `nfs-legacy`: This volume service is implemented with libfuse. It only supports NFSv3 and has some performance constraints.  This service is deprecated.
  
  Both services offer a single plan called `Existing`.
  
  