Avamar: Disk partition full but not due to 'cur' or checkpoint overhead (RESOLUTION PATH)

This article provides a resolution path where the disk partitions on an Avamar Utility Node or Data Nodes are becoming full.

• The size of the cur directory
• The amount of checkpoint overhead in the cp.XXXXXXXXXX directories (for data nodes)
• The presence of files that are expected or unexpected files. This could be due to user activity or undesirable behavior

See the child articles in the 'resolution' section for a list of possible causes.

If the node is a data node or a single node Avamar grid, check if the space consumed by 'cur' or checkpoint overhead is causing an issue: Avamar: Operating System (OS) Capacity (Resolution Path).

If the space consumed by 'cur' or checkpoint overhead is not the cause of the partition consumption, see Avamar: How to identify large files or directories consuming disk space on an Avamar node.

Once the large files or folders have been identified, review the articles below which describe how to solve the known scenarios:

• Avamar: /data01 partition fills up due to large files in /usr/local/avamar/var/mc/server_tmp and /usr/local/avamar/var/client directories
• Avamar: Data partition is full due to disk test files in QA directories
• Avamar: The grid enters admin mode due to differences in data partitions sparse files

• Avamar: No space left on device error due to the number of inodes