java.io.IOException: No space left on device

[morty]

I build some tycho MANIFEST first projects on Hudson ver. 1.396 using maven
3.0.3. But I start getting this error in the console:

[INFO] Scanning for projects...
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)
...
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
java.io.IOException: No space left on device

Some builds completes without error but other fail. Eg. I build an eclipse
product which fails, the log has the following to say:

!ENTRY org.eclipse.equinox.p2.publisher 4 0 2011-05-24 20:34:25.115
!MESSAGE Error publishing artifacts
!STACK 0
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)
at
java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161)
at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
at java.util.zip.ZipOutputStream.write(ZipOutputStream.java:272)
...
...
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

!ENTRY org.eclipse.equinox.p2.publisher 4 0 2011-05-24 20:34:25.563
!MESSAGE Error publishing artifacts
!STACK 0
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)

When I execute 'df' or 'du' on the disk I have plenty of space left (have
also checked the inodes). The build only fails on Hudson, building locally
works fine. Any ideas?

--
View this message in context: http://jenkins.361315.n4.nabble.com/java-io-IOException-No-space-left-on-device-tp3547971p3547971.html
Sent from the Jenkins users mailing list archive at Nabble.com.

[Youri Bonnaffé]

did you checked the disk space and inode usage during the build too ? I have similar issues with GWT compilation and it turns that a lot of disk space is needed during the compilation itself.

[morty]

How do you check for disk/inode usage during build?

--
View this message in context: http://jenkins.361315.n4.nabble.com/java-io-IOException-No-space-left-on-device-tp3547971p3548003.html

[morty]

Running df during the build gives different results:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 19891060 12636180 6252428 67% /
varrun 1948208 40 1948168 1% /var/run
varlock 1948208 0 1948208 0% /var/lock
udev 1948208 44 1948164 1% /dev
devshm 1948208 0 1948208 0% /dev/shm
/dev/sda3 30969600 16640608 12755828 57% /media/m2
overflow 1024 1024 0 100% /tmp

m@hudson:/media/m2$ df

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 19891060 12636376 6252232 67% /
varrun 1948208 40 1948168 1% /var/run
varlock 1948208 0 1948208 0% /var/lock
udev 1948208 44 1948164 1% /dev
devshm 1948208 0 1948208 0% /dev/shm
/dev/sda3 30969600 16639844 12756592 57% /media/m2
overflow 1024 848 176 83% /tmp

there is something called 'overflow' that changes from 100% to around 60%.

--
View this message in context: http://jenkins.361315.n4.nabble.com/java-io-IOException-No-space-left-on-device-tp3547971p3548021.html

[Manuel Doninger]

Seems that is your tmp partition. And obviously it also seems, that it
is to small. Try to increase it.

Manuel

[morty]

thanks I will give it a try.

--
View this message in context: http://jenkins.361315.n4.nabble.com/java-io-IOException-No-space-left-on-device-tp3547971p3548060.html

[Youri Bonnaffé]

while :; do sleep 5; df -h; done
an alternative might be to configure your build to not use /tmp for (this is the case with the GWT compiler, you can use the Maven target folder for instance)

[morty]

Hm when I look into the 'configure' section of my hudson job there is no
option to specify an alternative tmp directory - do you specify this in
hudson or in some settings in the pom file for the relevant project?

--
View this message in context: http://jenkins.361315.n4.nabble.com/java-io-IOException-No-space-left-on-device-tp3547971p3550476.html