From kdepim-users Tue Nov 15 17:16:30 2011 From: Stephan Diestelhorst Date: Tue, 15 Nov 2011 17:16:30 +0000 To: kdepim-users Subject: Re: [kdepim-users] Frequent coruptions of data base. Any remedies? Message-Id: X-MARC-Message: https://marc.info/?l=kdepim-users&m=132137747200750 On 13 November 2011 19:58, Andras Mantia wrote: > Stephan Diestelhorst wrote: > >>>> The MySQL folks suggest to dump the database and manually feeding the >>>> data back in there, maybe AKonadi could do that? >>> >>> Question is, how often? When? And that would double the amount of space >>> you need in the $HOME. >> >> Mmhhm, it seems that the idea was that one could dump the data base, >> even after it was corrupted and manually feed the data back into a new >> copy. > > Doing anything from akonadi side when the database is corrupted is already > too late. Best would be if MySQL would be stable enough to deal with such > cases. I have simulated and expierenced a few real hard shutdowns again, and it seems that the settings so seem to help. InnoDB sees that there had ben an unclean shutdown, but is apparently able to recover. Now, if this is just luck I do not know, but it is at least some circumstantial evidence that the settings help. >> But this does not sound very stable, either. Maybe Akonadi could >> watch for these errors and indicate to the user that only a cache was >> lost and delete and repopulate the database files, if all else fails. > > Detecting corruption and informing the user about the problem is a good > idea, indeed. Can you put the information about the problem with the > suggestion into bugs.kde.org, so it doesn't get forgotten (not all > developers watch the user list regularly)? Reported as https://bugs.kde.org/show_bug.cgi?id=286711 >> No, this is on a built-in laptop drive with a LUKS -> LVM -> Reiser >> stack. The problem here is the laptop dieing every now and then during >> suspend / resume, but I'd still have some sane behaviour in that case. > > Interesting, I also have to restart my computers from time to time due to > failed resume, but never had a problem with the akonadi database. I wonder > what in the stack is causing the InnoDB instability. I don't use LVM and use > Ext3/4 though... I know, I might be living in the past / on the edge with this setup ;/ Many thanks, Stephan _______________________________________________ KDE PIM users mailing list Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users