Bug 57342

Summary:	kmail corrupts mail folters when the disk drive is full
Product:	[Unmaintained] kmail	Reporter:	etkopa
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	nchip, richard
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description etkopa 2003-04-16 23:39:28 UTC

Version:            (using KDE KDE 3.1.1a)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2.2 
OS:          Linux

When I marked a particularly big mail folder (maildir) and applied filters - kmail crashed reporting something about disk being full. The disk _was_ full. Some mails in the folder got wiped out - either they had no subject, or were full of garbage. I have seen disk full problems in kmail before and would humby suggest some serious solution like the one in kget. In most cases kmail silently corrupts the folders without reporting a problem or giving the user the ability to retry after disc cleanup.

Comment 1 etkopa 2003-04-16 23:41:24 UTC

The kmail I use is form kde 3.1.1a copiled from SRPM package found on www.kde.org.

Comment 2 Ingo Klöcker 2003-04-18 19:02:41 UTC

Subject: Re:  New: kmail corrupts mail folters when the disk drive is full

The mail folders are most likely not corrupted. But the index files seem 
to be corrupted. Exit KMail, delete the index files of the affected 
folders (.Folder.index* for a folder with name "Folder") and then 
restart KMail.

Comment 3 etkopa 2003-05-03 18:09:01 UTC

Still I think kmail should report something, and allow the user to perform a disk 
cleanup.

Comment 4 Stephan Kulow 2003-09-20 20:31:14 UTC

out of disk failures are really sub optimal, but they do not crash

Comment 5 Sebastian Sauer 2003-11-18 16:49:01 UTC

*** Bug 67135 has been marked as a duplicate of this bug. ***

Comment 6 Till Adam 2004-07-18 16:15:33 UTC

*** Bug 81234 has been marked as a duplicate of this bug. ***

Comment 7 Michael Jahn 2004-07-26 20:14:15 UTC

If nobody disagrees, I will mark this as a duplicate of bug 50462.

Comment 8 etkopa 2004-07-27 09:33:03 UTC

50462 seems to be the same bug. Go ahead.

Comment 9 Michael Jahn 2004-08-31 11:15:40 UTC


*** This bug has been marked as a duplicate of 50462 ***