Community
Participate
Working Groups
Build Identifier: 20110615-0604 We are using Eclipse on Vista with the workspace on C: but all projects on a Samba mounted ZFS on Solaris. Since some time now there is the annoying behaviour that resources get out of sync in a fairly random fashion. When doing a CVS update or Team Sync there is a fair probability that it will complain about a few files: org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '...'. at org.eclipse.core.internal.localstore.FileSystemResourceManager.write(FileSystemResourceManager.java:1076) at org.eclipse.core.internal.resources.File.internalSetContents(File.java:321) at org.eclipse.core.internal.resources.File.setContents(File.java:360) at org.eclipse.core.internal.resources.File.setContents(File.java:464) at org.eclipse.team.internal.ccvs.core.resources.EclipseFile.setContents(EclipseFile.java:198) at org.eclipse.team.internal.ccvs.core.client.Session.receiveFile(Session.java:801) I don't blame Eclipse (appeared already in 3.6 and persists with 3.7) but I am at a loss where to look further (Windows / Samba / ZFS?). It would be helpfull to know what the actual mismatch is. Is it a seconds vs. millisecond resolution problem, a few seconds clock difference, or is one of the values zero? Could you please include the mismatching timestamp values in the message for diagnosing the root problem. Timestamp as long value would be fine. If you choose to format the timestamp, please display with milliseconds resolution. Reproducible: Sometimes Steps to Reproduce: 1.Touch file outside Eclipse 2.Open file inside Eclipse 3.Message should read: Resource is out of sync with the file system: '[filename]' ([timestamp] vs. [timestamp]).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
