https://bugs.kde.org/show_bug.cgi?id=406087
Bug ID: 406087
Summary: akonadictl fsck incorrectly reports success when
file_lost+found folder is absent
Product: Akonadi
Version: unspecified
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: bren...@quantumfurball.net
Target Milestone: ---
SUMMARY
I ran akonadictl fsck, it reported:
Found unreferenced external file: [...]
[...]
Moved 893 unreferenced files to lost+found.
However, I had deleted the entire file_lost+found folder after the last time I
did such a clean-up, assuming akonadi would recreate it when necessary. Not so,
apparently. The folder still doesn't exist after running akonadictl fsck. The
files have not moved. If I re-run akonadictl fsck, it reports the same
unreferenced files, and that (again) it moved them to lost+found. Looks like
storagejanitor.cpp neglects to check that the folder exists or the result of
the call to QFile::rename(), and so incorrectly reports success when the
operation actually fails.
akonadictl fsck works correctly after I create the folder.
EXPECTED RESULT
Create file_lost+found folder automatically and/or report failure to move the
files, not success.
ADDITIONAL INFORMATION
akonadictl --version reports 5.9.3 (apparently missing from the version list).
--
You are receiving this mail because:
You are watching all bug changes.
