https://bugs.kde.org/show_bug.cgi?id=370708
--- Comment #2 from turcovadio <turcova...@gmail.com> --- Hi, again As you know, it is possible to prevent the complete losing of information in a case of full disk. It is logical to lose some information in the case of creating new alarms (in a full disk scenario), but now what remains in a full disk scenario is the deleted alarms. All the active alarms disappear. I think it is a good policy, when updating new alarms, keep the old file, create a new one, and after being successful, change the old file to the new one. In a case of a crash or full disk, create the possibility to recover the old file. Of course this is not new to you. What you surely didn't remember is that the disks can become full. Anyway, Kalarm is a great program. Thank you for your reply. Luis Duarte 2016-10-16 17:41 GMT+01:00 David Jarvie via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=370708 > > --- Comment #1 from David Jarvie <djar...@kde.org> --- > KAlarm is probably not the only application which can potentially lose data > when the disk becomes full. This is due to the way that files on disk are > updated - unless it's just a case of appending data to the end of a file, > when > a file is updated it is completely rewritten in an empty part of the disk > and > then the old data is marked as free. This handled by the file system > itself, > and it may not be possible to prevent data loss in such cases other than by > creating a new file with the new data, checking whether that succeeded, and > then deleting the old file only if it did succeed. This may not be > compatible > with the way that Akonadi (which handles file updates) works. This needs > investigation. > > In the meantime, the best advice it to always keep backups of important > data, > and don't let your disk fill up completely. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
