Skip to content

Why do I receive an "EFS Disk Quota Exceeded" error when I connect to my EFS file system?

2 minute read
0

I receive the "Disk quota exceeded" error when I try to connect to my Amazon Elastic File System (Amazon EFS) file system.

Resolution

The disk quota exceeded error occurs for the following reasons:

  • You exceeded a quota on the disk.
  • You reached the Network File System (NFS) client quota. Amazon EFS doesn't support user disk quotas.
  • A user tried to open a file on an EFS file system that reached its quota.

For more information, see Quotas for NFS clients.

When you exceed a quota, you might also receive the following error messages:

  • When you exceed the number of locks, you receive the LockObtainFailedException error.
  • When you use a Java-based application and exceed the NFS client quota, you receive the write.lock: java.io.IOException error.

To get the list of open NFS files, run the lsof -N Linux OS command.

To get the list of locks in the local system, run the lslocks Linux OS command.

Prevent disk quota exceeded errors

To prevent a disk quota exceeded error, take the following actions:

  • Modify your application so that it doesn't exceed specific quotas for user accounts, open files, and process locks. To identify a specific quota, use performance monitoring tools, such as nfsstat and nfsiostat. For more information, see Using nfsstat and nfsiostat to troubleshoot NFS performance issues on Linux on the Red Hat website.
  • Split your workload across more instances so that you don't exceed an instance quota. Based on your NFS client, there are file usage quotas that might result in a disk quota exceeded error. However, this error also occurs when an EFS file that has more than 512 locks across all connected instances and users that access the file.

If you continue to receive disk quota exceeded errors, then contact AWS Support.

AWS OFFICIALUpdated 2 years ago