Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354201 - "no space left on device", again
Summary: "no space left on device", again
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-08 22:13 EDT by David Williams CLA
Modified: 2011-08-09 13:52 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2011-08-08 22:13:56 EDT
I know these reports are frequent, and often "clear themselves up" as cron jobs free up space ... but, I thought worth reporting ... after all, I heard something about "new file servers" recently? :) 

This was occurring, for me, for at least 15 minutes, around 10 pm Monday night (eastern). 

= = = = = 

Problems reported while synchronizing CVS Workspace. 0 of 1 resources were synchronized.
An error occurred synchronizing /webtools: The server reported an error: No space left on device
The server reported an error: No space left on device
webtools: cannot create_adm_p /tmp/cvs-serv14899/wst/api/org/eclipse/wst/common/modulecore

= = = = = =

The exact file involved would usually differ from one run to another. Other (smaller?) projects seemed to sync ok. 

I hope this report is helpful. 

Thanks,
Comment 1 David Williams CLA 2011-08-08 23:52:56 EDT
FWIW, my "sync" started working again by about 11:00 PM. Also, even when one machine (one instance of Eclipse) could not 'sync', I tried from another machine, and it could sync just fine ... thus, I guess, indicating one ?node? was having trouble, and other machine's connection just happened to semi-randomly get a good node? 

Again, hope it's helpful. Feel free to close as "working" if/when you'd like (that is, after you do, or decide not to investigate anything on servers). 

Thanks,
Comment 2 Eclipse Webmaster CLA 2011-08-09 09:55:24 EDT
Ok, we decided to fix this using our old friend ramdisk.  I've created and mounted a 4G ramdisk as /tmp on all of the dev machines.  This should eliminate the 'no space' errors when CVS/SVN is busy, and provide a performance gain.

-M.
Comment 3 Denis Roy CLA 2011-08-09 11:26:39 EDT
That is a good fix.  4G of tmp space not only quadruples what we had, but since it's a ramdisk anything that reads/writes to /tmp will be lightning fast.
Comment 4 David Williams CLA 2011-08-09 11:32:44 EDT
greatest thanks! Proof again that opening bugs works! :)
Comment 5 Carl Anderson CLA 2011-08-09 13:32:58 EDT
I just got something similar.  I brought up my Helios environment and tried to synchronize w/ the repository, and I ended up with 105 errors.  I was pointed to this bug, tried the synchronize again, and it worked.  All of the log entries are similar to:

!ENTRY org.eclipse.team.core 4 0 2011-08-09 13:23:32.078
!MESSAGE Problems reported while synchronizing CVS Workspace. 2 of 107 resources were synchronized.
!SUBENTRY 1 org.eclipse.team.core 4 0 2011-08-09 13:23:32.078
!MESSAGE An error occurred synchronizing /org.eclipse.jem.beaninfo: The server reported an error: No space left on device
!STACK 1
org.eclipse.team.internal.ccvs.core.connection.CVSServerException: The server reported an error: No space left on device
	at org.eclipse.team.internal.ccvs.core.client.Request.executeRequest(Request.java:176)
	at org.eclipse.team.internal.ccvs.core.client.ValidRequests.execute(ValidRequests.java:26)
	at org.eclipse.team.internal.ccvs.core.client.Session.open(Session.java:174)
	at org.eclipse.team.internal.ccvs.core.resources.UpdateContentCachingService.cacheFileContents(UpdateContentCachingService.java:224)
	at org.eclipse.team.internal.ccvs.core.resources.UpdateContentCachingService.buildRemoteTree(UpdateContentCachingService.java:118)
	at org.eclipse.team.internal.ccvs.core.resources.CVSWorkspaceRoot.getRemoteTree(CVSWorkspaceRoot.java:176)
	at org.eclipse.team.internal.ccvs.core.syncinfo.CVSResourceVariantTree.fetchVariant(CVSResourceVariantTree.java:78)
	at org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(AbstractResourceVariantTree.java:84)
	at org.eclipse.team.internal.ccvs.core.syncinfo.CVSResourceVariantTree.refresh(CVSResourceVariantTree.java:334)
	at org.eclipse.team.core.variants.AbstractResourceVariantTree.refresh(AbstractResourceVariantTree.java:54)
	at org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(ResourceVariantTreeSubscriber.java:162)
	at org.eclipse.team.core.variants.ResourceVariantTreeSubscriber.refresh(ResourceVariantTreeSubscriber.java:126)
	at org.eclipse.team.core.subscribers.Subscriber.refresh(Subscriber.java:466)
	at org.eclipse.team.internal.ccvs.core.CVSWorkspaceSubscriber.refreshWithContentFetch(CVSWorkspaceSubscriber.java:434)
	at org.eclipse.team.internal.ccvs.ui.mappings.WorkspaceSubscriberContext.refresh(WorkspaceSubscriberContext.java:305)
	at org.eclipse.team.core.mapping.provider.SynchronizationContext.refresh(SynchronizationContext.java:109)
	at org.eclipse.team.internal.ui.synchronize.RefreshModelParticipantJob.doRefresh(RefreshModelParticipantJob.java:69)
	at org.eclipse.team.internal.ui.synchronize.RefreshParticipantJob.run(RefreshParticipantJob.java:309)
	at org.eclipse.team.internal.ui.synchronize.RefreshModelParticipantJob.run(RefreshModelParticipantJob.java:117)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Contains: org.eclipse.jem.beaninfo: can't create temporary directory /tmp/cvs-serv13315
Comment 6 Eclipse Webmaster CLA 2011-08-09 13:52:53 EDT
My guess would be that your ssh session was still connected to the 'old' mount point (probably because sshd had an open file pointer) and so it wasn't using the new location.

I've restarted the sshd process, so let me know if the issue persists.

-M.