Email alerts report exports storage is almost full in Adobe Commerce
This article provides a solution for the issue where you receive an email stating that the exports storage is almost full.
Description description
Environment
Adobe Commerce on cloud infrastructure (all versions)
Issue/Symptoms
You receive an email with the following content, but are unable to locate the exports folder:
Our monitoring has detected that the ‘exports’ storage on your cluster XXX is around ‘85%’ full.
If needed, please review the usage, do a clean up, or request for an upsize.
Also, note that we will attempt an upsize automatically when storage reaches the critical-threshold level.
Root cause
The alert refers to the exports storage filesystem, which is the disk volume where media and other file data are stored. This filesystem is typically mounted at /data/exports. The alert does not indicate the presence of a single directory literally named exports.
To confirm what the alert refers to, check the exports storage usage:
-
Run
Shelldf -h | grep, and the following example output appears:code language-none /dev/nvme1n1 50G 38G 12G 77% /data/exports tmpfs 7.7G 4.0K 7.7G 1% /data/exports/shared -
In this example,
/data/exportsis the main exports filesystem:- 50 GB total
- 38 GB used
- 12 GB available (77% utilization)
/data/exports/sharedis atmpfs(in-memory) mount used for shared data and does not contribute significantly to disk pressure.
This confirms that the alert is triggered by the overall disk utilization of /data/exports, not by a single folder named exports. If /data/exports shows high utilization, large directories under this filesystem—such as pub/media or other custom file locations—are typically responsible for the increased usage.
Resolution resolution
Follow these steps to review, clean up, and validate exports storage usage.
-
Run the command
df -h | grep exportsto check the current usage of the exports storage filesystem. Review the Use% column for/data/exports:- If usage is 70–85%, start planning a cleanup.
- If usage is greater than 90%, take action immediately to avoid write failures or service impact.
-
Identify directories consuming significant disk space under
/data/exportsby runningdu -sh /data/exports/* 2>/dev/null. The typical locations where the file storage is likely to be filled up arepub/media/catalog/product/cacheorvar/logfolders.- Determine how many nodes there are in that instance (using magento-cloud CLI command:
magento-cloud ssh --all). - SSH to each node (command: ssh
(command: ssh <node>.ent-<project_id>-<production|staging>-<identifier>@ssh.us-X.magento.cloud)).
- Determine how many nodes there are in that instance (using magento-cloud CLI command:
-
Clean up files based on the environment:
- Remove old or unused export files, logs, or temporary data first.
- In non-production environments, you can usually remove test media or old artifacts more aggressively.
- In production environments, coordinate with your team before deleting any media or business-critical files.
-
After the cleanup, run the following command
df -h | grep exportsto confirm that the Use% value for/data/exportshas dropped to a safe operating level.