[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    [Bug 76942] file saving, consider vi like save to new file, unlink
From:       Kris Kersten <mmmbugs () gmail ! com>
Date:       2009-05-19 18:48:04
Message-ID: 20090519184804.D76F112040 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=76942


Kris Kersten <mmmbugs@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mmmbugs@gmail.com




--- Comment #28 from Kris Kersten <mmmbugs gmail com>  2009-05-19 20:47:59 ---
This bug causes MAJOR problems with a full disk situation.  I was running a
backup of some large data files, not paying attention to how much disk I had
left.  Unfortunately I ran out of space.  Before I realized this, I told Kate
to save the file I had been editing.

With backups enabled, this is what happened:

1) Kate deletes the old backup file and writes a new backup file.  With no disk
space.  Result:  an empty backup file
2) Kate then deletes the old working file and saves a new working file.  Still
no disk space.  Result: an empty working file

Net result:  In attempting to save to a full disk, Kate wipes BOTH the backup
and working files.

I intended to file a separate bug report, but the saving algorithm as described
in this bug report is certainly the cause of my empty files.  Although I must
add that it seems fairly short sighted to just _assume_ there is enough space
on disk to write the file.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]