This weekend I upgraded our FishEye/Crucible from 3.3.3 to 3.5.4.  Just to be safe, I first ran "tar cjvf FISHEYE_INST".  This operation took approximately 75 minutes and created a tar-ball that is 12Gb in size.  I was quite surprised to see such a large compressed file.  Is this normal?  Is there some operation I should be regularly running to trim our FISHEYE_HOME directory?

2 answers

Hi Neil,

The FISHEYE_INST directory holds all the data related to your repository cache, so depending on the size of your repositories, it may consume a big amount of space. Could you please confirm the original size of this directory?

By "original size" I assume mean the size of the directory, before tar'ing and compressing, right? "du -sh FISHEYE_INST" reports 23Gb, so yes, it's pretty large.  If that's normal, then I don't have a problem with it; I just wanted to make sure that there isn't some normal maintenance which I've been inadvertantly skipping.

Suggest an answer

Log in or Join to answer
Community showcase
Bridget Sauer
Published Mar 09, 2018 in Jira Service Desk

E.L. Fridge's take on education, Jira Service Desk, and creative Jira use cases

...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...

325 views 0 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot