Troubleshoot capacity issues

The following sections describe scenarios where an instance might encounter capacity issues and provides steps to help address the problem.

"No space left on device"

Check if the Filestore instance has sufficient inodes by running the following command on the client VM:

df -i

The command returns something similar to the following:

Filesystem           Inodes        IUsed      IFree         IUse%  Mounted on    134217728        13         134217715     1%     /mnt/test

Each file stored on the file share consumes one inode. If IUse% reaches 100%, you are not able to store more files on the file share even if you haven't reached the maximum allocated capacity. The number of inodes scales with capacity. If you want to add more inodes, you must add more capacity.

The following service tiers have a maximum capacity usage of approximately 89% of the provisioned capacity. The remaining capacity is reserved for internal operations and resources:

Service tier Maximum capacity usage limit?
Basic HDD Does not apply
Basic SSD Does not apply
Zonal with a lower capacity range Yes
Zonal with a higher capacity range Yes
Enterprise Yes

For details, see Known issues.

df and du commands report different amounts of free disk space

When a file that is open by a running process is deleted, the disk space that the file consumes does not get freed until the file is closed. The df commands accounts for the space consumed by deleted open files, whereas the du command does not. This difference in calculation is why the du command often shows more free space than df.

To display the deleted files that are still open by a running process, run:

lsof | grep deleted