https://bugs.kde.org/show_bug.cgi?id=456983

--- Comment #2 from ratijas <m...@ratijas.tk> ---
I'd like to add that akonadi restarts itself and keeps spamming those logs even
after explicitly being stopped with `akonadictl stop`. Maybe this setting is
not persistent between reboots?

Also why am I suspecting it was the cause of filesystem breakage? Because while
recovering, btrfs had problems with this particular file. Its metadata was
broken or something like that. Without the `--ignore-errors` option it wasn't
able to get past this huge log. I'd wish I could instruct btrfs-restore to skip
this file completely, but there is no such option currently.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to