Issue

  • VSs show up in read-only mode after being created.
  • The lvdisplay command shows that newly created LVM partitions are not available.
  • The newly created VSs show up in read-only mode even though everything is fine with the template.

Environment

OnApp 5x, 6x

NFS 4

Static and CloudBoot environments

NFS mounts on compute resources and backup servers:

/onapp/backups /onapp/templates
CODE


Resolution

To resolve the issue, use NFS3 instead of NFS4.

To switch back to NFSv3:

  1. SSH to the required compute resource.
  2. Check your currently mounted devices by running the mount command.

  3. As you can see, the version in use is version 4 (vers\):

    377.235.95.01:/onapp/backups on /onapp/backups type nfs (rw,vers=4,addr=377.235.95.01)
    CODE

  4. To switch these over to NFSv3, run the following:

    mount -o vers=3 nfs/path /directory
    CODE

    Please note that you should replace nfs/path and /directory with the correct information needed.

  5. Run the following command:

    mount -o vers=3 377.235.95.01:/onapp/templates /onapp/backups
    CODE

  6. Run the mount command to make sure the NFS mount has changed the versions successfully. The output will be similar to the following:

    377.235.95.01:/onapp/backups on /onapp/backups type nfs (rw,vers=3,addr=377.235.95.01)
    CODE

Cause

As of OnApp 5.0 and all earlier versions, NFS version 4 is not supported with our current layout due to some incompatibilities regarding attributes, permissions, etc. We recommend using NFS version 3, because NFSv4 does some extra attr checks in files. Therefore, when OnApp tries to mount the filesystem, it doesn't have the right attributions/permissions.

377.235.95.01:/onapp/templates on /onapp/templates type nfs (rw,vers=4,addr=377.235.95.01)
CODE