Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Monitoring Splunk
- :
- Minimum Free Disk Space Reached
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've Just set-up a new Single Instance Splunk Server (Version 7.3.2) on a VM with 200GB of space. I've not set up any indexes/searches/apps etc I've literally only run the installer and logged in to the web page.
Why am I getting the following error when I have so much free space on the VM?
"The minimum free disk space (5000MB) reached for /opt/splunk/var/run/splunk/dispatch"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you checked how that 200GB is configured in the VM's filesystem? Could it be that /opt is on a separate partition or so, and as such not able to make use of the full 200GB?
What does the df -h command tell you?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you checked how that 200GB is configured in the VM's filesystem? Could it be that /opt is on a separate partition or so, and as such not able to make use of the full 200GB?
What does the df -h command tell you?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the space for dispatch files is full. It is possible that splunk is not able to cleanup the files that is being generated, check this article, this will assist you to cleanup the dispatch directory or even adjust the limits.conf for this configuration.
-> https://answers.splunk.com/answers/389879/dispatch-directory-is-full-how-do-we-clear-it-up.html
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As was said above, it was a problem with my partitions. I resized the partition and it now works perfectly
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
[Puzzles] Solve, Learn, Repeat: Matching cron expressions
Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass
May 2026 Splunk Expert Sessions: Security & Observability
