When On-Premise the error "java.io.IOException: No space left on device" is shown

DESCRIPTION

You are getting a Java IO Exception regarding "No space left on device". That is a Java exception that any MuleSoft component could trigger since several Mule components require some minor file system usage based on some conditions.
The issue itself is not a direct MuleSoft related issue but you need to analyze your environment to identify the root cause.
Any software at that hardware could be exhausting your local storage, so you need to track the top consumers and identify if there is a sizing issue, a MuleSoft related files filling your file system, or something else. 

STEPS TO FOLLOW

Contact your SysAdmin to track the top consumer files or top consumer folders.

1) If you find the top consumer files in the $MULE_HOME/.mule/<api_name> folder, it could be a Batch Job related issue, and it could be working as designed (meaning a sizing issue) or a possible leak, depending on if the files are in the stepping queue internal folder, or the object store internal folder. For more info:
- No space left on device error for applications using batch processors
- What is the batch history used for in batch jobs
- How to modify the default frequency to delete expired Batch Job Instances metadata sooner
- Batch Object store files take up too much disk space

2) If the files are part of the /tmp folder, please validate that they belong to MuleSoft products or not first

3) If you find "mule-buffer-*" files in the /tmp folder, they should be generated by the Streaming Strategy you are using, so please analyze the files and identify the API generating them, it could be a sizing issue or you could tune that API to address that. For more info:
- Transferring multiple large files, in a cloudhub-deployed Mule 4 app, can result in this error: java.io.IOException: No space left on device
- Streaming Strategies

4) If the files are DataWeave related (dw-buffer-input-*, dw-buffer-output-* or dw-buffer-index-*), it could be a sizing issue, or a flow not consuming the stream as expected. Please take a sample of those files, analyze it and find out the API responsible of the creation of that file, then make the required modifications or proper sizing. For more information:
- DataWeave Memory Management

5) If you discover another file coming from a Connector developed by a third-party developer, please contact them. 

6) In case a temporary file is created, and a JVM outage happens (like an OutOfMemory event, a power outage, or an incident OS restart, etc), the reference to that file is broken and the runtime would not be able to remove it properly, so if you consider that you may have too many unreferenced files, you may stop the runtime, and delete them.

7) If you have some other folder or files consuming most of your file system and you are unable to locate them in this list, please engage your SysAdmin first, and if they confirm that they belong to the MuleSoft runtime process, please create a Support case and upload the file to continue.