Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

The Free space health check has failed in your system. notification appears in jira


"The Free space health check has failed in your system" this notification appears in jira dashboard. 

is this related to space issue?

is there any who faced similar issue. please help me in resolving this.

thanks in advance ! 

1 comment

Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 07, 2019

This is related to disk space.

I faced similar issue, I resolved it via

  1. Looking into logs and Jira Home. Some import places to look are,
    2. <JIRA_HOME>/export
    3. <JIRA_HOME>/log
    4. <JIRA_HOME>/caches
    5. <JIRA_HOME>/plugins/.osgi-plugins/transformed-plugins (this sometimes contain multiple copies of same plugin)
  2. Increasing size disk partition containing Jira Home directory.


Mostly cleaning JIRA_HOME will solve this issue.

While the error message is about disk space, it is actually very misleading. It says that the free space health check has failed to run, so the results (low disk space or not) could not be determined.


Misleading Error:


A potential cause for the error (slated for JIRA 8.1):


Hope this helps, JP


Log in or Sign up to comment