Bug 310109

Summary: akonadictl fsck: Cleaning up missing external file *
Product: [Frameworks and Libraries] Akonadi Reporter: Christian Mollekopf <mollekopf>
Component: serverAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: Martin
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Mollekopf 2012-11-14 17:30:33 UTC
I already had a couple of akonadictl fsck runs, which resulted in a bunch of of missing external parts to be found (mostly on items in (disconnected) imap resources I think, not sure if solely in such items though).
I have no idea how that can happen and the first guess of a faulty filesystem seems unlikely that I'm having these problems since months and the system is otherwise running just fine. I had to shutdown the computer a couple of time when sleep failed or so, so that could be one reason.

I'm not sure if we can avoid the problem, but we have to be able to deal with it at least. akonadictl fsck can already detect the missing files, and clear the payload, so it's downloaded again once the item is requested (we might want to do that right away as part of the fix).
At least with some views missing parts can block a whole collection from being viewed, e.g. in akonadiconsole where selecting a folder always results in an itemfetch of the fullpayload 1:*, meaning the job will fail even if only one single item has a missing external part and it cannot be downloaded atm.

So there might be several different approaches, such as doing partial fetches in ItemFetchJob, detecting the problem in the background and fixing it before somebody notices (e.g. running fsck on startup), or avoid the problem altogether if thats possible at all.

Reproducible: Sometimes
Comment 1 Denis Kurz 2016-09-24 20:41:10 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:09:00 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.