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

Low disk space on device containing temporary directory (/opt/atlassian/jira/temp)

Hi All,

I'm using official docker image for running Jira in datacenter mode. After starting the instances, I have below error under Instance healthcheck of "Troubleshooting and support tools"

Low disk space on device containing temporary directory (/opt/atlassian/jira/temp) - 2 GB of free space remaining. Index backup and recovery may fail.

This directory is under docker container and do not have much files inside it. I have enough space in shared home as well as jira local home which is mounted to EFS and EBS volumes. Is there anything I can do to troubleshoot and fix this error?




1 answer

1 vote
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 14, 2021

@radhika.punchepady  The application believes that there is not enough space.  I would suggest checking how large your index is and then making the proper adjustments to ensure that there is enough space available.  

Thanks Brant for answer. As I was having EFS and additional EBS for home directories, I missed to check root volume in server(that was silly). Resolved issue after extending root volume.  

Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events