Community
Participate
Working Groups
Created attachment 118047 [details] error log To reproduce: 1. Choose 'New - Project... - Plug-in Project' (I've also reproduced using 'New C Project' with the same steps as below) 2. Enter a project name, in the attached error log the project name is 'p8' 3. Unselect 'Use default location' and enter a path to a samba mounted drive. I've noticed some other bugs when handling resources in the root of a samba drive, so in this case I've chosen a non-root folder, H:\folder\p8. H: is a mapped network drive to a folder on an ubuntu 8.04 server. 4. Click 'Next' and then click 'Finish' 5. At this point an error dialog opens with an 'Access denied' error. However, looking in the log (attached) I can see that the root problem was 'File not found'. At this point I can also see that the H:\folder\p8\.project was created, but is nearly empty. Doing a cat on the linux system shows that it has project name, but no buildSpec or natures. ae@bass:~$ cat folder/p8/.project <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>p8</name> <comment></comment> <projects> </projects> <buildSpec> </buildSpec> <natures> </natures> </projectDescription> 6. Click 'Finish', to get another 'Access Denied' error. 7. Click 'Finish' again and the creation completes. NOTE: Clicking cancel in either step 6 or step 7 causes the temporarily created .project file to be deleted. The attached error log is from a session within RSM 7.5 (running on J9), however I have reproduced this on plain Eclipse 3.4 (on Sun's JVM) as well.
I just encountered this issue on Windows 7 and Windows 10 with Eclipse Neon.2 (and also Luna and Mars). While in plain Eclipse, I can apparently just click OK and the project gets created anyway, this is different when I'm using KNIME [1] which is built on Eclipse: creation of a new KNIME workflow results in a project that can not be saved in a consistent state due to the error messages from this issue. Is there any known solution/workaround?
After some debugging, we found that the issue is apparently caused by eclipse trying to set the I=Indexed attribute which on the given network storage is not supported. See also this report on the KNIME forum: https://tech.knime.org/forum/knime-general/file-system-errors-when-using-workspace-on-network-drive
That one seems to be open for years. It is now 2021 and I have the same problem. I could track it down on Windows 10 with Process Monitor. So would it be solved or is there a workaround ?
