Why am I receiving an "EFS Disk Quota Exceeded" error when connecting to my file system?
Last updated: 2022-11-15
I'm receiving a "Disk quota exceeded" error when attempting to connect to my Amazon Elastic File System (Amazon EFS) file system. How can I troubleshoot this error and prevent it from happening again?
The Disk quota exceeded error message occurs when a limit on the disk is exceeded. This occurs when you hit the Network File System (NFS) client limit, because Amazon EFS doesn't support user disk quotas. Or, this error occurs when a user tries to open a file on an EFS file system that reached its limit. For more information, see Quotas for NFS clients.
You might also receive the following error messages when you exceed a limit:
- LockObtainFailedException: This error might occur if the number of locks is exceeded.
- write.lock: java.io.IOException: This error might occur if you exceed an NFS client quota when using a Java-based application.
Prevent disk quota exceeded errors
To prevent exceeding disk quotas, do the following:
- Identify a specific limit. You can use performance monitoring tools such as nfsstat and nfsiostat. For more information on these tools, see the Red Hat page Using nfsstat and nfsiostat to troubleshoot NFS performance issues on Linux. Modify your application so that it doesn't exceed specific limits, such as for user accounts, open files, and process locks.
- Split your workload across more instances. Depending on your NFS client, there are various file usage limits that might result in a Disk quota exceeded error. However, there's only one limit shared across all clients that leads to this error. Specifically, a file can have up to 512 locks across all instances connected and users accessing that file. Therefore, by splitting the workload across more instances, you reduce the chances of reaching an instance's limit.
If you continue to receive disk quota exceeded errors after following the steps above, contact the AWS support team for additional troubleshooting.