To resolve this issue, verify that there is sufficient space in the vCloud Director virtual machine transfer cache directory's file system. If you require additional space for virtual machine imports and exports, mount an NFS volume internal to the vCloud Director virtual machine.
Also, ensure that the NFS folder is set with read and write permissions.
To check the permissions:
- Log in to the vCloud Director with root credentials.
- Change directory to /opt/vmware/vcloud-director/data/transfer.
- Run this command to test the read and write permissions:
touch /opt/vmware/vcloud-director/data/transfer/test
Note: If the test fails, the directory must be remounted with read/write permissions. This requires the vCloud Service Management to be shutdown.
To shutdown vCloud Service Management:
- Change directory to /opt/vmware/vcloud-director/bin.
- Run this command:
In vCloud Director 5.1:
./cell-management-tool -u username -p password cell --shutdown
In vCloud Director 1.5:
./cell-management-tool -u username -p password cell --shutdown
You must also ensure that the supplemental shared storage volume meets these requirements:
- It must be accessible to all servers in a vCloud Director cluster.
- When using NFS, this volume must have write permission for vCloud Director.
To change permissions, run this command:
chmod -R 775 /opt/vmware/vcloud-director/data/transfer
- Each vCloud Director host virtual machine must mount this volume:
$VCLOUD_HOME/data/transfer, typically /opt/vmware/vcloud-director/data/transfer.
Note: Uploads and downloads occupy this storage for a few hours to a day and the transferred images can be large. Therefore, allocate at least several hundred gigabytes to this volume.