Maven repository cannot be indexed - No Space left on device

Answered

While Idea is trying to index my Maven repositories one of them (https://oss.sonatype.org/content/repositories/releases/) fails. The error given is java.io.exception: No space left on device

 

I have run df -h (I'm running on Linux) and none of my drives (including tmpfs) are running at above 61%

I thought I simply needed to resize the root partition, but, having done that the problem still exists.  Any suggestions

14 comments
Comment actions Permalink

What's the free space amount in /tmp?

1
Comment actions Permalink

This may be not enough since Lucene library index can be quite large.

You can try overriding IDE temp location by adding `-Djava.io.tmpdir=/some/other/partition` into .vmoptions (https://intellij-support.jetbrains.com/hc/articles/206544869).

1
Comment actions Permalink

I did that and, judging by the large number of idea related files appearing in the new tmp directory - it seem that it was successfully pointing to the new directory.

Unfortunately, this didn't seem to fix the problem either - despite the fact that the partition containing the new tmp directory has 115G available!

I'd also like to take the opportunity to thank you for your help on this issue so far.

1
Comment actions Permalink

Do you still see other files appearing in the old /tmp directory when indexing is performed? If you monitor /tmp space, does it get lower during indexing?

1
Comment actions Permalink

Try adding the same tmpdir property to the following settings:

http://i.imgur.com/bGkEVhj.png
http://i.imgur.com/a16k3z4.png

1
Comment actions Permalink

My IDE folders  are located in my /home directory (~/.IdeaIC2016.2/) and there are 115GB available on that partition.

It's also the partition with the largest amount of free space,so it's difficult to see where else I should be putting these folders...

0
Comment actions Permalink

I've uploaded idea.log to https://gist.github.com/phunni/8e700eb0a9a6198dd2df2ff6a22e1e36 

I've looked at the relevant stack traces and can't see anything helpful.

0
Comment actions Permalink

According to "df -h" it's 3.8G free and 1% in use of 3.9G total

0
Comment actions Permalink

Just running it again now and it's undoubtedly still using /tmp for the update even though idea itself is also clearly using my new tmp directory for it's temporary files.

I can see files with names such as nexus-maven-repository-index.gz4345089487902300119 in the /tmp directory. Since starting the process /tmp use has gone from 1% to 43% so far.

So pointing the VM to a new tmp directory worked as far as it went - except the update process doesn't seem to use the same tmp directory...

0
Comment actions Permalink

Wow - fast reply - thanks!

Index is still running so I can't definitively claim success yet, but those nexus-maven-repository-index.* files are now appearing in the new tmp directory and df- h indicates that /tmp use is not increasing at all.

I'll report back when the index has finished, but it looks like we've cracked it! Thanks again for your help - very much appreciated.

0
Comment actions Permalink

Index finished successfully - thank you again.

0
Comment actions Permalink

Thanks for the information.

0

Please sign in to leave a comment.