Apache OpenOffice (AOO) Bugzilla – Issue 58215
Input/Output error on opening or saving documents
Last modified: 2005-12-14 13:12:52 UTC
This problem has many faces and may be connected with issue 54136. Linux is meant to be Debian 3.1 Sarge (stable) and OOo20 sk build. 1. document (dosen't matter the type) on Samba 3.14 share is opened correctly from Linux OOo. When it comes to auto-save or user save, sometimes he gets "Input/output" error and document is not saved. In contrast to issue 54136, it is NOT dependent on opening the same document simultaneously from Windows machine. Occurs rather frequently (we have about 30 Linux machines here) but we cannot tell, what is the factor here -sometimes no error occurs and the document can be saved nicely. When error occurs, the document is probably not possible to save even under different name, because even if the new document is created, sometimes it is empty. Thus there is DATA LOSS. 2. We've gotten the same error on WindowsXP machine opening a file from Thunderbird e-mail message. The file for sure was not ever opened by other user. Again, we're not able to reproduce. It occurs quite randomly from our point of view. 3. Linux NFS v3 share. Document cannot be even OPENED from such share. This can be reproduced everytime -no chance to open document from NFS share. OOO 1.1.4 and 1.1.5 never displayed such behaviour. We strongly consider reverting back to OOo 1.1.4, there is amount of files created under 2.0 however that could produce problems (OOo 1.1.5 cannot save to OpenDocument, so users could be annoyed by using again other format for save, and we have instructed them already to use OpenDocuments). Moreover, we created system MIME assignments for all files to OOo2 and would take lot of futureless backwards steps to revert to OOo1.1.4. Without trying to be offensive, we'd be thankful to have an errata 2.0.1 release ASAP, since this bug is killer for us (and must be for everyone who organises his documents on network). Fortunately, not many users use OOo20 intensively, but such of them who do, they are far from success with using OOo2.0.
And of course, if OOo2.0 crashes entirely upon saving the document, there is "recovery" on next startup. But usually with not very useful results (all current work lost).
Correction from affected user: in point 2, it was not opened from mail but brobably from network share too. System was WindowsXP. So we can assume that this error is _network_share_related_. What has changed on shared files handling since 1.1.5? Where the bug creeped in? Could it be resolved reasonably fast to give our users "good" OOo2.0?
In summary this seems nothing to do with the wordprocessor. From my point of view you should have the same behavior with calc and or draw/impress. Is it?
You're right, spreadsheet gives the same results. However I don't see better cathegory for this. In the past, there has been "import" or so cathegory.
Not quite, an issue which is application independent, has to get the category "Framework" to be assigned to the right person in charge.
.
tuharsky, Is this possibly a duplicate of issue 54567? It looks very similar, at least, but you are running Linux whereas issue 54567 deals with Mac OS X. Take a look, anyway.
Yes, it looks like the same. I'm going to try the workaround suggested. I have no permission to perform necessary changes however. Would You do it, please? Changes on 54567: Platform:All OS: All Version: OOo 2.0 Summary: Input/Output error on network-shared documents
Please wait until I can look at results of workaround. The main concern is, if it helps with NFS. If yes, then it's probably the same issue.
The 54567 looks like our bug, but the workaround dosen't help completely even on SMB share (more detail in 54567 thread). I have had no opportunity to test the NFS case but I will do that this week, hope so. Wait until then, please.
I can confirm, that for NFS, the workaround works. Files now can be opened. Please, perform the changes on 54567 and mark this one as duplicate. 54567: Platform: All OS: All Version: OOo 2.0 Summary: Input/Output error on network-shared documents Status: NEW Because of very unpredictable behaviour and probable data loss, I'd very advice milestone it ASAP. I know it's quite hard, but I don't see it inappropriate to mark such a severe bug for milestone: 2.0.1
Hm, maybe the OOo version in 54567 could stay as it is now.
duplicate *** This issue has been marked as a duplicate of 54567 ***
closed as duplicate