To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=91015 Issue #|91015 Summary|data loss with new file locking mechanism in OOo3 Component|framework Version|OOo 3.0 Beta Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|mav Reported by|clutz
------- Additional comments from [EMAIL PROTECTED] Tue Jun 24 12:03:25 +0000 2008 ------- I tested the filelocking implementation of OOo3 (300m2 Rev 9301) on Windows and found the following scenarios which lead to data loss: No File locking for doc-files shared via samba-share: 1) Open a .doc-file that is hosted on a samba-share on Windows-host A 2) Open the same .doc-file on Windows-host B --> file opens editable (!!!BUG!!!) 3) edit the document on host A, save and close the document 4) edit the document on host B, save and close the document result: changes done in 3) are lost! The file-locking for .doc-Files on windows is broken. Another issue affects the file-locking in a heterogenous environment with a file shared via samba-share, opened in OOo3 on Windows and in OOo2 on linux with cifs-mount (the bug is reproducible with .doc AND .odt-files): 1) Open a .odt/.doc-file on a Windows host A with OOo3 2) Open the same .odt/.doc-file on a linux-client B with OOo2 --> file opens editable (!!!BUG!!!) 3) edit the document on host A and B and save the document. result: the last save-actions wins, the changes of the first save-action are lost. We currently migrate a lot of our PCs from MSO to OOo. In this time there are a lot of (alien) documents and templates that have to be shared within both office-suites. Besides the OOo-migration, we also introduce linux on an increasing amount of hosts, so we will have a completely heterogenous environment with a mix of MSO, OOo2, OOo3, Windows, Linux, Samba-Shares in which data loss will occur regulary with the current implementation. As the same scenarios do not cause data loss with the old implementation of OOo2, I think we cannot introduce OOo3 until this issue is fixed. Thank you very much for the great work with the new file locking with the temporary lock-file which seems to be very promising and might solve a lot of our most important issues, but I think the following adjustments have to be done: a) file-locking for alien-formats: The best handling for MSO-formats would be to use temporary lock-files compatible with the lock-files that MSO use. If this cannot be implemented due to some reason I think the next best alternative would be to reactivate the old OOo2 implementation for these kinds of files. b) compatibility with old OOo2-file locking is required: That means that all kind of files that are opened with OOo3 must be locked in a system-level way that OOo2 also recognizes and denies to open the file editable. Due to the weakness of OOo2 in that situation also a "select filter" or an "I/O-Error" message would be correct as long as OOo2 denies the editable access. Please add these two scenarios to your testcase and ensure that there is no way to lose data using OOo3. --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
