Eclipse: "Periodically save the workspace." ran into a problem. "

Question

I am using Eclipse Indigo on Mac 10.7.4. While working, I get these periodic, annoying dialogs

'Periodic workspace save.' has encountered a problem. Could not write metadata for '/.org.eclipse.jdt.core.external.folders'. /Users/davea/Dropbox/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/.org.eclipse.jdt.core.external.folders/.markers.snap (No such file or directory) 

I seem to be continuing normally, but I was wondering how I can fix these errors.

Answer 1

I had the same problem.

'Saving a periodic workspace.' ran into a problem. Failed to write metadata for '/ External Files'. D: \ Java \ Fuentes \ .metadata \ .plugins \ org.eclipse.core.resources \ .projects \ External Files \ .markers.snap (El sistema no puede hallar la ruta especificada)

I created the External Files folder and it worked perfectly. After a few minutes, the ".markers.snap" and ".syncinfo.snap" files appeared in this folder, and the message no longer appeared.

Answer 2

Today, I faced the same problem sequentially, whenever I step out of an eclipse. After trying the above solution provided by TS.xy, the steps below got rid of this problem.

• Switch to the new workspace and close Eclipse.
• Open Eclipse with a new workspace and after that switch to the actual workspace (which has an exception).
• Actual workspace loaded with all my previous projects.
• Exiting Eclipse now does not throw this exception.

Hope this step might work for someone.

Answer 3

I fixed mine by closing eclipse and deleting the entire .metadata folder inside my workspace folder.

Answer 4

For just another data point, none of the above actions helped my situation. How I finally overcame this problem is that every time Eclipse complained that some folder was not there, I went to my hard drive and created a folder. For example. after i see

 Could not write metadata for '/servers'. C:\...\.metadata\.plugins\org.eclipse.core.resources\.projects\servers\.markers.snap (The system cannot find the path specified.) 

I create the "servers" folder (and not the file inside it). This will lead me to the following error. I went through 3-4 of these iterations (leaving Eclipse each time to force save) before the problems disappeared.

HTH, Mark

Answer 5

Using Ubuntu got the same problem. I noticed that the owner of some of the directories in ~ / workspace / .metadata / .plugins / ... etc .... was the root changed the owner to me, and the error stopped.

It seems that the same problem can be caused by several reasons.

Answer 6

Close Eclipse, completely empty the .metadata folder. Launch Eclipse and import the necessary project again if the links to the project are deleted.

Answer 7

I ran into the same problem, I decided to rename the folder name in the workspace folder. those. com.ibm.collaboration.realtime.alertmanager.embedded was renamed com.ibm.collaboration.realtime.alertmanager.2embeddedxx and my project was rebuilt.

Answer 8

It was just for me -

Decision

• (pre) the specified directory is missing, see fig.
• Launch Eclipse, see the error shown in fig. below. Close eclipse

• Create the directory (RemoteSystemsTempFiles) where it looks

  • note: ignore items in this folder (e.g. .markers), they are automatically generated

• Restart Eclipse, the problem is resolved!

Problem Report Example

I don’t know why it took me so long to decide, but it’s pretty easy now and quite obvious in retrospect!;) ...

Answer 9

In my case, since I accidentally deleted the folder with the workspace, and I noticed that "Periodic saving of the workspace has encountered a problem." To solve this problem, I just create a new workspace and upload all my projects to a new one. Hope you can solve your problem by doing the same.

Answer 10

I also ran into this problem. My situation was a little different. I used "work sets" to group my projects inside eclipse. What I did was try to delete the project and get errors when deleting. Ignoring the errors, I deleted the project from my working set and, therefore, did not see that I even had a project. When I got my error, I didn’t think I was looking through my batch explorer with “projects”, unlike working sets, like my top view. After moving to the top level of the projects, I discovered that the project was half deleted and was able to delete its contents both from my workspace and from the hard drive.

I have not had a mistake since.

Answer 11

I solved it by setting the workspace in the local folder and setting the data from the import project from existing resources.

Answer 12

I was too aggressive about deleting some directories in my project area when I was running out of disk space and deleted that directory. Eclipse can leave some huge kernel files if it crashes in your workspace directories (I had 35 gigs), so sometimes you need to look there in your workspaces.

In any case, in accordance with the problem, I tried the "create directory" approach. And it worked.

I also saw this error when I closed Eclipse, by the way, not only after the "periodic save". So exit / restart was also part of this.

Please note that the last element in the directory path indicated in the error message is a file, not a directory, so do not confuse here. It is probably worth checking the correctness of creating permissions for directories (like other projects in the workspace, which I think).

Obviously, this is a mistake in the Eclipse code base (creating the full path to the directory under the created file), but if I had not deleted it first, I would not have called it first,

Answer 13

I have the same problem since yesterday. Yesterday I fixed this by creating a new workspace and re-importing the projects. It seemed to work well, but today it started again.

So, today I created the folder and file manually and gave full permissions -rwxrwxrwx.

Seems to work again ...

Answer 14

Close Eclipse. Open the RemoteSystemsTempFiles folder in the workspace and uncheck it inside this folder. Close the eclipse again and close, warn about .project. Click Ok, then open Eclipse. Solved my problem.

Answer 15

Today I encountered this problem after they switched our anti-virus software to Kaspersky.
In my case, the platform is Windows 7. My workspace is stored on a mapped network drive. The strange thing is that although this is a permission issue, I can manipulate files and folders at the same level as an inaccessible file without incident. So far, the only workarounds have been moving the workspace to a local drive or uninstalling Kaspersky. Uninstalling and reinstalling Kaspersky without the firewall function did not help.

I will update this answer if and when we find a more suitable solution, although I expect this to require anti-virus software settings, not Eclipse.

Answer 16

In my case, the disk on which I stored my workspace completely downloaded the SDK updates, and I just needed to free up space on it.

Answer 17

This happened to me because I deleted one of the resource files inside the .metadata folder in my workspace.

After trying all the methods, delete the .metadata folder in my workspace.

Infact, this Nuke option seems to work when there are many problems associated with eclipse errors. One such example is work sets. Working sets are extremely distorted (but useful), and that is where most of my eclipse problems begin.

Hope this helps someone.

Answer 18

I solved the problem of switching workspace.

• Go to file (switch workspace)
• Select a destination and create a folder called Workspace
• Launch Hello World and close Eclipse (note that Eclipse automatically creates the RemoteSystemsTempFiles folder)
• now copy all your projects to the new Workspace folder
• Open Eclipse and if necessary (sometimes Eclipse does not show projects) imports all of them (go to File / Open projects from the File System)

Answer 19

After exiting the eclipse, a specific error will occur. My point is that DISK is FULL , so the eclipse can no longer write to it.