Summary: | Akonadi corrupted after hard reboot | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | springer |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | critical | CC: | dvratil, springer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Akonadi self test report on startup. |
Description
springer
2013-12-10 14:18:02 UTC
Created attachment 84022 [details]
Akonadi self test report on startup.
Sorry, but how is this a bug? If you forcibly shutdown system with database stored on a network storage, you cannot expect anything else than database corruption. Either don't store ~/.local/share/akonadi with MySQL data on NFS, use system (or remote) MySQL instance, or use SQLite (but you will pay horrible performance penalty there if you use KMail). Closing as invalid, as this is not a bug report or a feature request and nothing we can do about in Akonadi. Sorry. |