Known Issues and limitations
Contributors Download PDF of this topic
The following known issues and limitations exist in Cloud Volumes Service for AWS.
Issue: If an existing volume only supports NFSv3, and a volume is created or converted with NFSv4.1 or both NFSv3 and NFSv4.1 support, then the existing volume may not be mountable without specifying the NFS version (vers=3).
Workaround: Either add the option to specify the NFS version to the mount command, for example,
mount -o vers=3 …or ensure all volumes are converted to support NFSv4.1. Note that Linux clients will default to NFSv4.1 unless the version is specified.
Issue: Creating a new volume from a snapshot may fail with the message 'Unable to set volume attribute "files" for volume <volume> … Reason: New count must be larger than current allocated count of <number>'.
Workaround: This issue occurs when trying to create a volume from a snapshot that currently has more files allocated to it than the new volume would be assigned for its allocated capacity. You must increase the allocated capacity for the new volume to assign enough files (inodes). See Selecting the allocated capacity for details.
Issue: The network virtual interfaces will be deleted automatically in CVS regions that have no volumes after 72 hours. When creating a new volume, you will need to re-provide the AWS account # and CIDR.
Workaround: To avoid the network virtual interfaces from being deleted during periods of inactivity, leave at least one volume and lower the allocation and service level to minimize cost.
Issue: Users with expired subscriptions cannot log in to the Cloud Volumes Service user interface or interact with the API.
Workaround: Go to the AWS Marketplace page for the Cloud Volumes Service and renew your subscription.