Bug 113138 - FILESAVE general input/output error on save, files truncated
Summary: FILESAVE general input/output error on save, files truncated
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: dataLoss
Depends on:
Blocks:
 
Reported: 2017-10-15 17:05 UTC by heseltine.michael
Modified: 2019-05-16 13:58 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description heseltine.michael 2017-10-15 17:05:12 UTC
I fully expect this to be useless, as I cannot give an exact way to reproduce the error but here it goes anyway: 

For several x64 versions, up to 5.4.1.2 (which I'm currently using), Writer and Calc have destroyed my work on several occasion by suddenly saying "general input/output error" to all tries to save the file currently open. When this happens, I can only close the program (losing all changes made till my last backup). The file I tried to save to is truncated to zero bytes, though I can't say whether it was truncated by the save that caused the aforementioned error, or the one before that. 

The error appears without rhyme or reason, but always on file save, and seems to occur quicker and/or more often when I save more often (which I did to lose less work in between saves, to no avail). 

The problem has occured on two different Win10 professional installations on two different computers, with files of vastly different sizes, but always created with one of those LO installations. I have tried several LO versions, but the problem persists. 

If this happens, nothing can be saved (even after restarting LO or the whole machine) until I delete the user profile for LO. After that, I can use the suite again for a few minutes to a few days until the problem reappears. The files however, are gone. All I can do is get the backups and redo the changes.

I'm usually saving the files in question to a newwork drive (SMB share or SFTP drive using ExpandDrive or MountainDuck), but once the error occurs, the file can't be saved to any drive, be it remote or local. 

This seems to be related to a number of bugs reports of both LO and OO going back up to seven(!) years, e.g.

https://forum.openoffice.org/en/forum/viewtopic.php?f=6&t=65222
https://ask.libreoffice.org/en/question/90888/draw-general-inputoutput-error-while-saving-document/
https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=71300
http://nabble.documentfoundation.org/General-input-output-error-when-saving-to-network-drive-td3061786.html

I have stopped using LO for now as I can't afford to lose any more time or files with this.
Comment 1 Buovjaga 2017-11-07 13:21:02 UTC
(In reply to heseltine.michael from comment #0)
> I'm usually saving the files in question to a newwork drive (SMB share or
> SFTP drive using ExpandDrive or MountainDuck), but once the error occurs,
> the file can't be saved to any drive, be it remote or local. 

Has it ever happened when saving to a local drive?
Comment 2 Timur 2017-11-07 17:54:17 UTC
(In reply to heseltine.michael from comment #0)
> This seems to be related to a number of bugs reports of both LO and OO going
> back up to seven(!) years, e.g.
There were different network issues, some of these are Linux, like Bug 99667.
Windows had bug 67534. And some Netware like Bug 81556.
But generally network works. You have to find why it doesn't in you case "(SMB share or SFTP drive using ExpandDrive or MountainDuck)".
Comment 3 Xisco Faulí 2018-01-09 11:18:56 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2018-07-31 09:38:32 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2018-09-03 14:57:19 UTC Comment hidden (obsolete)
Comment 6 Stéphane Aulery 2019-05-13 11:53:59 UTC
From: Stanislav Maslovski <stanislav.maslovski@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: impossible to save file: General input/output error
Date: Sun, 24 Feb 2019 14:51:26 +0000

Package: libreoffice-writer
Version: 1:6.1.5-1
Severity: important

Hi,

After a recent upgrade from Debian stable to testing I am getting a
very strange error in LibreOffice Writer, when trying to save a
document to the local hard drive. This never happened to me before on
this machine. To reproduce the bug, I just need to continue working on
a file and periodically press the Save button.

The error appears when trying to save the document. When working on
the text, I periodically click the "Save" button (a habbit I have from
the time when computers were big enough to fit a room, and
unreliable enough to destroy your work in a sudden freeze).
Anyway, after a series of succesfull saves, this strange error appears,
after which it is only possible to close the application and accept
the loss of the recently entered data.

I did a search on the internet, and found that some people experienced
the same problem before, notably, when saving to a network drive.
Let me stress, that here this problem appears when saving to the local
HDD. You can check, for example, this bug report:

https://bugs.documentfoundation.org/show_bug.cgi?id=113138

His simptoms are similar to mine, however, I do not have to erase the
LO profile in order to be able to save files in LibreOffice again.
Just closing and opening the application is enough, however, of
course, the recently entered data are lost anyway. Also, when this
error happens, the file length is not truncated to zero, and the file
still has the content from the last successfull save.

As this problem results in a loss of data, I set the severity of this
bug as important. 

BR,

Stanislav
Comment 7 Buovjaga 2019-05-13 12:07:16 UTC
I guess we'll set to NEW, but it would be helpful for Stanislav to be present in this report. Otherwise I don't see this moving anywhere as more information is clearly required.
Comment 8 Stéphane Aulery 2019-05-13 12:14:14 UTC
Indeed, I send a message to him to encourage him to participate in the discussion on this report. If nothing moves, it falls back into limbo.
Comment 9 Timur 2019-05-13 14:37:43 UTC
Stéphane's issue in Debian is unlikely related to Michael's in Windows. 
There are some strange bugs in Debian like Bug 124607.
Comment 10 Xisco Faulí 2019-05-16 13:58:02 UTC
Changing severity back to medium until we hear back from Stanislav