Bugzilla – Full Text Bug Listing
| Summary: | Revision graph fails with java.io.FileNotFoundException: .../.metadata/.plugins/org.eclipse.team.svn.revision.graph/repositories.data (No such file or directory) | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Jörg Thönnes <jtk499> |
| Component: | Revision Graph | Assignee: | Igor Burilo <igor.burilo> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | a.gurov |
| Version: | 0.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Jörg Thönnes
I have check this functionality several times but not even once I have had issues like this. So, I think the issue is related to the access rights on the file system (I've seen already similar reports quite a time ago) and in order to solve the problem please make the folder accessible for modifications. Sorry for the late reply, but it looks like there is some security issue: file access rights were changed so that the revision graph could not open this file for write anymore. Could you check it please if it is not too late? (In reply to comment #2) > Sorry for the late reply, but it looks like there is some security issue: file > access rights were changed so that the revision graph could not open this file > for write anymore. Could you check it please if it is not too late? Дорогой Александр, I have no idea how the access could be changed. I am using Linux and the workspace is in my home directory. Maybe you could tell me some background information how this could happen or some better ways to debug this issue if it reappears. Спасибо, Jörg Exception happened at the first line of the code:
PrintWriter out = new PrintWriter(file, "UTF-8");
try {
................
} finally {
out.close();
}
There is only one reason why it could happen: file could not be opened for write and could not be created. Why it could happen? I could think up a few reasons:
1) file exists, but has no rights for write/read
2) file does not exists, but can't be created due to security restrictions
3) instead of file there is a directory with the same name
4) file exists, have all required rights, but locked by another process
Situation 3) should not be happening because it requires manual intrusion (delete file, then create directory with the same name).
Situations 1), 2) and 4) could happen but when and why - I actually have no idea.
So, this is all possible reasons for the code to fail, I can think of.
> 1) file exists, but has no rights for write/read > 2) file does not exists, but can't be created due to security restrictions > 3) instead of file there is a directory with the same name > 4) file exists, have all required rights, but locked by another process Do you lock this file on Linux? > So, this is all possible reasons for the code to fail, I can think of. Maybe reason 2b) Lack of disk space... OK, if it happens the next time, I will check according to your ideas. Cheers, Jörg > Do you lock this file on Linux? No. > Maybe reason 2b) Lack of disk space... It is possible, but unlikely. It is not something you could occasionally overlook (because no one likes working with only few kilobytes of disk space available :) ). (In reply to comment #5) Hello Jörg, As it seems the issue is not reproduced in such a long time, I suppose it really was a case > 2b) Lack of disk space as you suggested. So, for now I'll close the report as one that doesn't require a fix. |