Bug 61255 - FILEOPEN: File opening shows that file is corrupted when /tmp is full, locked file afterwards
Summary: FILEOPEN: File opening shows that file is corrupted when /tmp is full, locked...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Spreadsheet (show other bugs)
Version: 3.6.5.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-22 00:41 UTC by Rodolfo Quesada
Modified: 2013-03-01 18:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Rodolfo Quesada 2013-02-22 00:41:32 UTC
Problem description: I tried to open a spreadsheet file unaware that my /tmp directory was full (a ramdisk), so LibreOffice showed me a dialog that said that the file is corrupted and it should attempt to fix it and to not trust the contents afterwards. It was unable to do so. 

I cleaned my /tmp directory and then proceeded to copy the file to another location and it opened without any issue and intact details. 

Also, a ".lock....name_of_file" locked the filename in the directory and I needed to remove it manually in order to have a file with the same name as the locked file. 

Steps to reproduce:
1. Fill the /tmp partition/directory (this is common in distributions as ArchLinux that uses a ramdisk, otherwise the hard drive should be full)
2. Open a file
3. Errors will appear and the .lock file should be removed manually. 

Current behavior: A lock file blocks the manipulation of a file with the same filaname in the same directory. LO says that the file is corrupted but it isn't. 

Expected behavior: It shouldn't say that the file is corrupted if the error is LO unable to create a temporary file in /tmp (I guess that's what happened). A lock file should be removed if there isn't an open session. 

Thanks for a great product and the amazing work you guys have done!

              
Operating System: Linux (Other)
Version: 3.6.5.2 release
Comment 1 Michael Meeks 2013-03-01 18:44:22 UTC
I've seen problems like this when low on space. There are so many potential failure modes - that IMHO we should check free-space and warn before doing any load/save of this kind - as well as improving this warning.

Thanks for the report :-)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.