Bug 328628 - Akonadi corrupted after hard reboot
Summary: Akonadi corrupted after hard reboot
Status: RESOLVED NOT A BUG
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 14:18 UTC by springer
Modified: 2013-12-10 16:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Akonadi self test report on startup. (14.37 KB, text/plain)
2013-12-10 14:19 UTC, springer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description springer 2013-12-10 14:18:02 UTC
After  a hard reboot that was necessary due to an issue with the NFS server containing the home directory, Akonadi fails to start up. The only resolution found so far was to delete .local/share/akonadi/ and .config/akonadi and redo the configuration. So far, this kind of hard reboot was necessary twice while kmail was running, every time resulting in the described issue.

Self test log attached below.

Reproducible: Always




Operating system is OpenSuse 12.3 with all software components from the official repositories. Home directory is on NFS server running Ubuntu 12.04.
Comment 1 springer 2013-12-10 14:19:14 UTC
Created attachment 84022 [details]
Akonadi self test report on startup.
Comment 2 Daniel Vrátil 2013-12-10 16:04:33 UTC
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.