trying out akonadictl fsck gives me: milian@minime:~$ "Looking for resources in the DB not matching a configured resource..." Known resources: ("akonadi_pop3_resource_0", "akonadi_notes_resource_0", "akonadi_maildispatcher_agent", "akonadi_ical_resource_0", "akonadi_imap_resource_0", "akonadi_imap_resource_1", "akonadi_maildir_resource_1", "akonadi_mailfilter_agent", "akonadi_archivemail_agent", "akonadi_imap_resource_2", "akonadi_kalarm_resource_0", "akonadi_kalarm_resource_1", "akonadi_kalarm_resource_2", "akonadi_nepomuk_feeder", "akonadi_contacts_resource_0") "Looking for collections not belonging to a valid resource..." "Checking collection tree consistency..." "Looking for items not belonging to a valid collection..." "Looking for item parts not belonging to a valid item..." "Looking for overlapping external parts..." "Verifying external parts..." "Found 87306 external files." "Found 87306 external parts." "Found no unreferenced external files." "Looking for dirty objects..." "Collection "Search" (id: 1) has no RID." "Found 1 collections without RID." "Item "51109" has no RID." ... now a few hundred of these lines with different item numbers ... "Item "93706" has no RID." "Found 524 items without RID." "Item "17360" has RID and is dirty." "Found 1 dirty items." "Consistency check done." Now what? Shouldn't something be done with the items that have no RID? Reproducible: Always
Still happening in 2016 with the latest software
Still happening in 2017.
Still happening in 2018 :-) :-(
Confirmed with Akonadi 17.08.3. Please see Bug 360834 - no mechanism to reattempt to store items without rid (just in db) into the resource and the thread akonadictl fsck: What messages indicate real issues and what to do about them? https://marc.info/?l=kdepim-users&m=149426877926602&w=2 (I am about to reply to this thread with a mail with more findings and more references to bugs report about akonadictl fsck I newly created.) for the best information on these messages I got so far. So far I am not aware of any fix, so you could only attempt to fix it up manually. Which for me is no viable option considering that I have >3000 of these messages with a local maildir resource.