Build failing with "no space left on device"
We use RTC for code development and for promoting code from Development to QA to Production.
Out of the blue, suddenly our builds for moving the pieces around are failing with what appears to be disk space issues in the error messages. This happens when moving stuff from the local repository workspace into the stream, or when going from the stream to the Dev server or from the stream to the QA server or whenever. Below is an error message that is typical of what is going on.
None of the machines involved have any actual shortage of disk space in any of the volumes, /tmp included. The fact that it suddenly started doing the same thing everywhere, when it wasn't doing it through yesterday, leads me to believe it is not actually a disk space issue anywhere but that is the way some issue is interpreted by the RTC system.
If anybody may know what is going on I'd really appreciate a pointer. I looked over scores of different questions and answers on here so far and haven't been able to come up with anything solid to go on.
I am not a java maven myself, but I am pretty experienced with 'using' RTC to facilitate the editing and promotion ina fairly involved set of projects.
2015-04-02 15:40:57 [Jazz build engine] running on host: co9053112151
2015-04-02 15:40:57 [Jazz build engine] Should build occur?
2015-04-02 15:40:57 [Jazz build engine] Yes: Always build a user initiated request.
2015-04-02 15:40:58 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm"
2015-04-02 15:40:58 [Jazz build engine] Accepting changes into workspace "CIP Development continous build Workspace" ...
2015-04-02 15:41:00 [Jazz build engine] Deleting fetch destination "/home/isstspt/build/iscip" before fetching ...
2015-04-02 15:41:01 [Jazz build engine] Fetching files to fetch destination "/home/isstspt/build/iscip" ...
com.ibm.team.build.internal.scm.SourceControlUtility$3: Status ERROR: com.ibm.team.filesystem.client code=0 There were errors during download. It is recommended that components be reloaded. The reload will be incremental, loading only the missing items. You can further reduce the reload time by reloading just the projects out of sync. null children=[Status ERROR: com.ibm.team.filesystem.client code=0 Failed to download /Documentation/documentation/Architecture Design Artifacts/ISCIP Infrastructure Architecture.pdf com.ibm.team.repository.common.InternalRepositoryException: No space left on device]
at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:693)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:238)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:934)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:740)
at java.lang.Thread.run(Thread.java:853)
Contains : 0 Failed to download /Documentation/documentation/Architecture Design Artifacts/ISCIP Infrastructure Architecture.pdf
com.ibm.team.repository.common.InternalRepositoryException: No space left on device
Out of the blue, suddenly our builds for moving the pieces around are failing with what appears to be disk space issues in the error messages. This happens when moving stuff from the local repository workspace into the stream, or when going from the stream to the Dev server or from the stream to the QA server or whenever. Below is an error message that is typical of what is going on.
None of the machines involved have any actual shortage of disk space in any of the volumes, /tmp included. The fact that it suddenly started doing the same thing everywhere, when it wasn't doing it through yesterday, leads me to believe it is not actually a disk space issue anywhere but that is the way some issue is interpreted by the RTC system.
If anybody may know what is going on I'd really appreciate a pointer. I looked over scores of different questions and answers on here so far and haven't been able to come up with anything solid to go on.
I am not a java maven myself, but I am pretty experienced with 'using' RTC to facilitate the editing and promotion ina fairly involved set of projects.
2015-04-02 15:40:57 [Jazz build engine] running on host: co9053112151
2015-04-02 15:40:57 [Jazz build engine] Should build occur?
2015-04-02 15:40:57 [Jazz build engine] Yes: Always build a user initiated request.
2015-04-02 15:40:58 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm"
2015-04-02 15:40:58 [Jazz build engine] Accepting changes into workspace "CIP Development continous build Workspace" ...
2015-04-02 15:41:00 [Jazz build engine] Deleting fetch destination "/home/isstspt/build/iscip" before fetching ...
2015-04-02 15:41:01 [Jazz build engine] Fetching files to fetch destination "/home/isstspt/build/iscip" ...
com.ibm.team.build.internal.scm.SourceControlUtility$3: Status ERROR: com.ibm.team.filesystem.client code=0 There were errors during download. It is recommended that components be reloaded. The reload will be incremental, loading only the missing items. You can further reduce the reload time by reloading just the projects out of sync. null children=[Status ERROR: com.ibm.team.filesystem.client code=0 Failed to download /Documentation/documentation/Architecture Design Artifacts/ISCIP Infrastructure Architecture.pdf com.ibm.team.repository.common.InternalRepositoryException: No space left on device]
at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:693)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:238)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:934)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:740)
at java.lang.Thread.run(Thread.java:853)
Contains : 0 Failed to download /Documentation/documentation/Architecture Design Artifacts/ISCIP Infrastructure Architecture.pdf
com.ibm.team.repository.common.InternalRepositoryException: No space left on device
2 answers
Check out this post.
https://jazz.net/forum/questions/175813/edc5133i-no-space-left-on-device-during-dependency-build
Reloading will not help. Make sure you have enough space for "/home/isstspt/build/iscip".
https://jazz.net/forum/questions/175813/edc5133i-no-space-left-on-device-during-dependency-build
Reloading will not help. Make sure you have enough space for "/home/isstspt/build/iscip".
...and of course this morning the RTC builds are all working like normal...
nothing changed on any of the targets but everything is working like it is supposed to.
Sunspots, right?
nothing changed on any of the targets but everything is working like it is supposed to.
Sunspots, right?
Comments
Kevin van Houten
Apr 02 '15, 5:13 p.m.