Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316719 - Unable to write metadata to .markers.snap
Summary: Unable to write metadata to .markers.snap
Status: CLOSED DUPLICATE of bug 294854
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 02:13 EDT by Thomas Hallgren CLA
Modified: 2012-04-02 09:34 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Hallgren CLA 2010-06-14 02:13:09 EDT 
Build id: I20100603-1500

My IDE can be completely idle and when I get back, I have a dialog "Problem Occurred" with the following text:

Could not write metadata for '/TP'.
/home/thhal/workspaces/build-3.6/.metadata/.plugins/org.eclipse.core.resources/.projects/TP/.markers.snap (No such file or directory).

I find nothing in the log.
Comment 1 Szymon Brandys CLA 2010-06-14 06:28:19 EDT 
This happens when IOException is thrown while saving makers snapshots, see SaveManager#visitAndSnap line 1674. I'm not sure what is the cause of this IOException though. 

Does it happen always once the workspace is corrupted? Reproducible steps would help of course.
Comment 2 Thomas Hallgren CLA 2010-06-14 08:32:55 EDT 
The setup is fairly complex so it's not easily reproducible. My guess is that it is related to using an external mechanism to add files to an otherwise empty project. I.e.

1. Create a new workspace.
2. Create a new general project
3. Use some external tool to put files into the project folder. Do not refresh!
4. Restart your IDE and wait

The only reason I can find for an IOException at line 1674 is that the attempt to write .markers.snap is performed without first creating the containing folder.
Comment 3 Szymon Ptaszkiewicz CLA 2012-04-02 09:34:56 EDT 
I can reproduce it using Java Project. Your TP project must have been renamed/moved and the information about rename/move was not persisted in workspace metadata before workspace corruption happened. After restart, an action that required periodic workspace save happened and after some time, when the periodic save occurred, the error was shown. This is a duplicate of bug 294854.

*** This bug has been marked as a duplicate of bug 294854 ***