Bug 302499 - Akonadi's MySQL database gets corrupted very easily
Summary: Akonadi's MySQL database gets corrupted very easily
Status: RESOLVED DUPLICATE of bug 286711
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-25 10:53 UTC by SZÉKELYI Szabolcs
Modified: 2013-03-02 21:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SZÉKELYI Szabolcs 2012-06-25 10:53:49 UTC
If Akonadi or the computer crashes, it's very likely that the underlying MySQL database is left in a corrupt state, and Akonadi fails to start for the next time. The only solution is to delete the database, which yields a complete resync of e-mail folders, for example, that can take several hours leaving the user without e-mail access for that long.

This fragile nature of the database should be addressed. Maybe by using a more robust backend, or by somehow forcing the MySQL server to keep data in a consistent state on disk.

Reproducible: Sometimes

Steps to Reproduce:
Pull the plug from the computer (happens).
Actual Results:  
Akonadi Server Self-Test reports 'MySQL server log contains errors' when KMail is started for the next time.

Expected Results:  
It should tolerate errors like this.
Comment 1 Daniel Vrátil 2013-03-02 21:11:30 UTC

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