anchor.diff:      {
        "credentials": {},
        "label": "nfs",
  -     "name": "nfs_service_instance",
  +     "name": "nfs\_service\_instance",
        "plan": "Existing",
        "provider": null,
  -     "syslog_drain_url": null,
  +     "syslog\_drain\_url": null,
        "tags": [
         "nfs"
        ],
  -     "volume_mounts": [
  +     "volume\_mounts": [
         {
  -       "container_dir": "/var/vcap/data/153e3c4b-1151-4cf7-b311-948dd77fce64",
  -       "device_type": "shared",
  +       "container\_dir": "/var/vcap/data/153e3c4b-1151-4cf7-b311-948dd77fce64",
  +       "device\_type": "shared",
          "mode": "rw"
         }
        ]
  
positive.code: owner: Core Services
  ---
  
  This topic describes how Cloud Foundry (CF) app developers can read and write to a mounted filesystem from their apps. In CF, a volume service provides volumes so your app can read and/or write to a reliable, non-ephemeral file system.
  
  ## <a id="pre"></a> Prerequisite
  
  Before you can use a volume service with your app, your CF operator must [add a volume service to your deployment](./deploy-vol-services.html).
  
  You can run `cf marketplace` from the Cloud Foundry Command Line Interface (cf CLI). The below is an example output of the NFS volume service. If there is no volume service that fits your requirements contact your CF operator.
  
  ```
  service   plans      description
  nfs       Existing   Service for connecting to NFS volumes
  ```
  
  ## <a id="create"></a> Create and bind a Service Instance
  
  To use a volume service deployed by your operator, you must first create an instance of the specific volume service needed service. Follow the procedures below:
  
  1. <a href="../devguide/services/managing-services.html#marketplace">Create a service instance.</a>
  
  <p class="note"><strong>Note</strong>: When using the NFS volume service, an extra parameter `share` is required by using the `-c` flag and a JSON. This parameter forwards what NFS server and share is needed for the service to the broker.
    E.G.: `cf create-service nfs Existing nfs_service_instance -c '{"share": "10.10.10.10/export/myshare"}'
  
  1. <a href="../devguide/services/managing-services.html#bind">Bind the service to an app.</a>
  
  <p class="note"><strong>Note</strong>: When using the NFS volume service, two extra parameters are needed `gid` and `uid`. This again can be specified by the `-c` flag and a JSON. This parameter specifies what `gid` and `uid` should be used when mounting the share to the application.
    E.G.: ` cf bind-service my-app nfs_service_instance -c '{"uid":"1000","gid":"1000"}'
  ## <a id='app'></a> Access the Volume Service from your App
  
  To access the volume service from your app, you must know which file path to use in your code. You can view the file path in the details of the service binding, which are available from the [VCAP_SERVICES](../deploy-apps/environment-variable.html#view-env) environment variable. Follow the steps below.
  
negative.code:   }
    </pre>
  
  2. Use the properties under `volume_mounts` for any information your app needs. Refer to the following table:
    <table>
      <tr>
        <th>
          Property
        </th>
        <th>
          Description
        </th>
      </tr>
      <tr>
        <td><code>container\_dir</code></td>
        <td>String containing the path to the mounted volume that you bound to your app.</td>
      </tr>
      <tr>
        <td><code>device\_type</code></td>
        <td>The NFS volume release Currently only supports `shared` devices. A `shared` device represents a distributed file system that can mount on all app instances simultaneously.</td>
      </tr>
      <tr>
        <td><code>mode</code></td>
        <td>String that informs what type of access your app has to NFS, either read-only `ro`, or read and write `rw`.</td>
      </tr>
    </table>
  