Bug 415271

Summary: akonadi does not create the file_lost+found folder
Product: [Frameworks and Libraries] Akonadi Reporter: Stefanos Harhalakis <v13>
Component: serverAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: minor CC: wbauer1
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In: 5.10.1

Description Stefanos Harhalakis 2019-12-17 01:52:38 UTC
It seems that akonadi does not create the file_lost+found directory which results in "akonadictl fsck" failing to move files there.

See here: https://github.com/KDE/akonadi/blob/ed93384ff692a684a1ade9bbc283ba495c0b3fe3/src/server/storagejanitor.cpp#L460-L466

There isn't anything that creates the directory.

In my case, I was running fsck continuously without any effect. The result was like this:
Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/56/5634856_r0
Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/27/7826627_r0
Found unreferenced external file: /home/v13/.local/share/akonadi/file_db_data/08/5711008_r1

And then:
Moved 105853 unreferenced files to lost+found.

But nothing was being moved. Then, once I created it by hand, it moved 3.8GB

I tried restarting akonadi in case it creates the directory, but nothing

I'm using akonadi server 4:18.08.3-7 (debian testing).
Comment 1 Wolfgang Bauer 2019-12-17 07:53:05 UTC
(In reply to Stefanos Harhalakis from comment #0)
> I'm using akonadi server 4:18.08.3-7 (debian testing).
That's not "GIT (master)" though, but rather 5.9.3 (which is over a year old and no longer available in bugzilla's version field).

The problem however was fixed already in 18.12.1 (5.10.1):
https://cgit.kde.org/akonadi.git/commit/?id=28f2916db1a2ad98b00250eb4d5dd92ca1548c50