To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=116690 Issue #|116690 Summary|OOo eats files when /tmp runs out of space Component|Word processor Version|OOo 3.2.1 Platform|Opteron/x86_64 URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|save-export Assigned to|writerneedsconfirm Reported by|pegasus
------- Additional comments from pega...@openoffice.org Fri Jan 28 14:13:53 +0000 2011 ------- My environment: Ubuntu 10.10 x64, separate / and /home partitions. Scenario: working for two weeks on three documents, saving along the way every few hours. Getting ready to wrap up, I want to verify some wording against the fourth document that I have to open again. Suprisingly, I get "general input/output error". I think oh wtf, it's 4am, lets finish this. I try to save each document one last time, I get "this document is locked; open readonly, open copy, cancel" message. I think wtf again, delete lock files for each, save, quit. Then I want to tar everything up and send my work to client, I notice that all three file sizes are 0. Instead of pulling my hair out I analyzed what happened. It took me a while ... Apparently ubuntu updater installed a new kernel image just hours before I finished my work, filling up all available space on the / partition (hitting the reserved 5% so non-root users could not write to /tmp anymore, but updater running as root figured it still has enough space to do its job). OOo writer then couldn't create new temporary files in /tmp, so opening of fourth document failed with most useless error msg imaginable. I'm not familiar with internals of OOo, but file locking code also seems to fail when /tmp is full. When I deleted lock files, its lock check succeeded, but apparently all files go through /tmp first without checking for any returned erros and are then happily written to their proper place. Therefore all I got was empty files. At no point in the process OOo writer hinted at being short on disk space. This is absolutely unforgivable. All this time /home had over 50GB disk space available. Folks, it's little things like this that make OOo a laughable product when compared to "serious" office suite. Please audit all your code and verify that you properly handle all possible errors returned from file io calls and then make sure that you properly present them to the user so the user can figure out how to solve the problem. Remember, user's data are holy and you must do everything in your power not to lose them. As things stand now, this is not the case. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
