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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,455,289
Community Members
 
Community Events
175
Community Groups

When building my artifacts, I tend to compress the files, and today I received the following error in my build:

gzip: stdout: No space left on device

So I checked my overall disk usage, and I use maybe 50/300 GB.

I proceeded with a "df" and the following was returned:

CKoDLIl

I must admit, my linux foo is not very strong, but to me, it seems like something is wrong, if a partition is 99% used, and the OS is complaining there is no more space.

So I went to the bamboo admin, and went to check how many builds and deployments were stored.

I decreased the numbers, deleting 6 builds, and 13 deployments.

I went to use df again, but this numbers here didn't change.

I tried google, but the only reasonable suggestion, was to change the partition size.

And this is the point where I'm no longer sure of what I'm doing, or, if this is even the issue.

Do you have any recommendations/tips for me? :) 

2 answers

1 accepted

2 votes
Answer accepted

This is not really an Atlassian problem, just one of housekeeping a build server.

But it is one many of us run into a lot. 

I would recommend trying to work out where the problem is - find an answer to "what is eating all my disk space?"  The df command is excellent for telling you overall usage, but it has a far more powerful friend called du

Go to the root of the partition (in your case, it looks like a single disk, so "cd /") and as root, run "du --max-depth 1".  This will tell you which directories are biggest, so you can descend into each of them and repeat the command. 

My usual mistake is to not set up "log rotate" for /opt/atlassian-stuff, but another good one is having a system that errors a lot spitting out way too much data into /var/log (I've got a broken postfix on one of my home machines that's currently clobbering /var/log/mail*.log for about 2% of the disk every day...)

1 vote

Hi Mikkel,

One extra piece of information that may help explain your situation - Linux will often keep a  % of your partition available for root, this could explain why df is showing 99% used but the application is unable to write to it.

either way, running on 1% available is obviously risky!

Work through the suggestions from @Nic Brough -Adaptavist-  above to find where the space is going to and clean up.

 

CCM

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events