Issue 24848 - OOo deletes files if disk is full.
Summary: OOo deletes files if disk is full.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-27 10:31 UTC by osavill
Modified: 2004-03-19 13:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2004-01-27 10:31:54 UTC 
I was using GNumeric and every time I tried to save the file I was met with an
empty error box ! so I decided to use OOo instead. The error dialogues were, as
expected, much more informative. They told me that the disk was full, so the
network admin people cleared some space on the drive (which is SAMBA mounted).

The problem was that now GNumeric told me that it didn't understand the file
format. Assuming that maybe OOo had written it out in sxw format (as per an old
OR) I loaded the file into OOo and was presented with a blank piece of paper as
if I had just done Document --> New.

On inspection of the file it had been reduced to 0 bytes ! This is very bad news
!! I have raised this as a priority 1 since under no circumsatnces should OOo
irevocably delete a file first prior to saving. If GNumeric and M$ Office can
cope with this situation then OOo must be able to as well. I assume that this is
an issue with all OOo save operations but I am not prepared to experiment !
Comment 1 Olaf Felka 2004-01-28 09:14:24 UTC 
This definitely not a P1 issue. Sure, it's dataloss but dataloss is not P1. P1
should be used for an usable office. This dataloss only occures under very
special circumstances and in times of 100GB harddrives it's very special. AFAIK
this is fixed for 1.1.1. I don't know if this fix has reached 1.1.1a. The expert
for these issue is lucky to enjoy his vacation these day. Please be patient.
Comment 2 thorsten.martens 2004-02-11 12:28:54 UTC 
Problem has already been fixed as far as the temp-folder (eg. /tmp) is not on
the volume with empty disc space. For example: Volume A is the system volume
with the temp-folder and enough disc space... and the user tries to save on
volume B (which hasn´t enough free space) -> an error message will occur and no
data is lost. But if A has runned out of space and the user tries to save, a
data.loss occurs. This problem will be fixed in the next milestone.

As far as this is an already known problem and an internal task exists, this
issue is set to invalid (because it can´t be set to duplicate of an internal
task) but it is a duplicate ! of course !

Thanks !
Comment 3 thorsten.martens 2004-03-19 13:33:22 UTC 
.