Community
Participate
Working Groups
Build Identifier: 20100617-1415 When user exceeds disk quoata at the local file system and tries to save an edited file Eclipse behaves normally. No information about error is given. In case of rewritng an existing file, all the data in the file is lost. Reproducible: Always Steps to Reproduce: 1. Hit the quota limit at the file system. 2. Edit a file. 3. Try to save it.
Moving to Platform-text.
Which editor?
Also, can you give a bit more details about "Other" in the Platform field? Thanks.
(In reply to comment #2) > Which editor? I was using text editor with CDT. (In reply to comment #3) > Also, can you give a bit more details about "Other" in the Platform field? > Thanks. Platform is: CentOS release 5.2 (Final) As far as i know it's linux based, but I'm not really sure.
>I was using text editor with CDT. But you used the default Text Editor and not a CDT (text) editor? You can check this by opening the context menu > 'Open With'. Thanks.
(In reply to comment #5) > >I was using text editor with CDT. > But you used the default Text Editor and not a CDT (text) editor? You can check > this by opening the context menu > 'Open With'. Thanks. It was CDT editor.
OK, could you test with the normal Text Editor? That would be great.
Using the normal text editor, it behaves the same way.
>When user exceeds disk quoata at the local file system and tries to save an >edited file Eclipse behaves normally. That's not what I see. I get the following dialog: https://bugs.eclipse.org/bugs/attachment.cgi?id=132923. Don't you get that dialog? Anything in the log? On what kind of file system is the file? The general issue about destroying the file is bug 3328 but as said, you should get a dialog.
I don't see that dialog. The problems are: 1. There is a disk space, just the quota is exceeded. 2. It's an mounted NFS, but for example VIM shows message about the error.
Anything in the .log?
I have hit the quota, exit eclipse - got an error that snapshot file couldn't be written), cleared the log, run eclipse again, reproduced the error and my log file looks like this: Framework arguments: -product org.eclipse.epp.package.cpp.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.cpp.product !ENTRY org.eclipse.core.resources 2 10035 2010-08-02 13:23:49.369 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.core.resources 4 567 2010-08-02 13:23:49.371 !MESSAGE Could not read snapshot file. !STACK 0 java.io.EOFException at java.io.DataInputStream.readInt(DataInputStream.java:392) at org.eclipse.core.internal.resources.SaveManager.restoreSnapshots(SaveManager.java:911) at org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:666) at org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1503) at org.eclipse.core.internal.resources.Workspace.startup(Workspace.java:2134) at org.eclipse.core.internal.resources.Workspace.open(Workspace.java:1883) at org.eclipse.core.resources.ResourcesPlugin.start(ResourcesPlugin.java:406) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:370) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:417) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:265) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:106) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:453) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:393) at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:33) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:466) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:116) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) !ENTRY org.python.pydev.core 4 4 2010-08-02 13:23:56.04 So there is no information about error during saving file.
Either there's an issue with NFS or out of disk quota is not handled correctly.
There's hardly any possibility that the NFS is a problem, because other editors handle with the situation correctly.
>There's hardly any possibility that the NFS is a problem Not with the NFS but how it's handled in Eclipse or the Java API implementations.
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie.
