On Friday 29 May 2015 16:36:59 Peter Humphrey wrote: > On Friday 29 May 2015 16:19:38 Mick wrote: > > On Friday 29 May 2015 10:36:37 Peter Humphrey wrote: > > > I had two sets of problems: one in KDE which I might have nailed > > > finally [1], and one at boot time in which /dev/md7 (RAID-1 with > > > metadata > 1.0) was not being started. > > > > > > [1] Whenever I've had KMail screw up I've created a new user and > > > re-imported its 14,000 e-mails, and until this latest time I've copied > > > the .mozilla directory from the old user to the new. This time I did > > > not, and so far all looks rosy. I'm not counting any chickens yet > > > though. > > > > Did you try deleting the akonadi database file(s) and restarting it > > instead of creating a new user? You will have to be patient, probably > > let it run overnight to asynchronously sync and re-index all your > > messages. > > I don't think I dare risk it: > > $ find . -name \*akonadi\* | wc > 49 49 2665 > $ find . -name \*akonadi\*dat | wc > 13 13 901 > > How would I know which to delete and which to leave alone? No, it may be > more work to start again with a clean slate, but at least I can be > confident of not screwing anything up too badly.
This is how I would try it out: 1. Create a back up of your complete /home. 2. akonadictl stop 3. Rename/move ~/.local/share/akonadi/db_data/ (or delete it since you now have a back up of this mess). 4. akonadictl start. Then go and make a brew, because this can take some time. I have hundreds of thousands of messages, so mine takes forever. I even thought of deleting most of my Google messages to accelerate this process, if I ever move to Kmail2. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
