[Kde-pim] possible data loss issue: empty mails, payload empty (1byte) (was: KDEPIM-2 from KDE SC 4.10.2 - first impressions)

[Martin Steigerwald]

On Saturday 13 April 2013 14:41:26 Martin Steigerwald wrote:
> On Saturday 13 April 2013 12:37:18 Martin Steigerwald wrote:
> > On Friday 12 April 2013 13:22:01 Martin Steigerwald wrote:
> > > On Friday 12 April 2013 13:16:59 Martin Steigerwald wrote:
> > > > As said, I can deal with those. My first impression is that
> > > > expecially
> > > > the  feeding of mail data into Nepomuk via the Akonadi Nepomuk
> > > > Feeder
> > > > creates responsive issues which I wouldn´t expect on a ThinkPad T520
> > > > with
> > > > dual corse Sandybridge i5-2520M mobile processor and Intel SSD 320.
> > > > 
> > > > I now let it sit at the state:
> > > > 
> > > > Akonadi Nepomuk Feeder:
> > > > Nepomuk is not operational: Nepomuk is not running
> > > > 
> > > > (while is currently indexes files and thus for sure is running.)
> > > > 
> > > > Once Nepomuk finished the mails I will dare to restart the agent.
> > > > Anyway,
> > > 
> > > > thats another issue:
> > > This is already reported as:
> > > 
> > > Bug 318110 - akonadi-nepomuk-feeder isn't detecting Nepomuk properly
> > > when
> > > system boots.
> > 
> > I found some more issues, also it seems to be mainly related to
> > responsiveness and performance.
> 
> Replying to myself again.
> 
> *sigh* I found a possible data loss issue:
> 
> [Akonadi] [Bug 318290] New: Empty mails:
> AkonadiAgentServer(4890)/libakonadi Akonadi::ResourceBase::itemRetrieved:
> Item does not provide part "HEAD"/"RFC822"
> 
> http://bugs.kde.org/318290
> 
> And thing is: I cannot even tell for sure whether its a data loss issue or
> Akonadi being confused. And I have absolutely no idea how it happened.
> 
> 
> Before doing anything else, I am now snapshotting my maildir directories
> again and create a complete backup after having migrated to KDEPIM-2
> backup.
> 
> 
> I think KDEPIM-2 as of KDE SC 4.10.2 still needs serious performance /
> responsiveness and more importantly correctness / robustness work. Its
> personal data it stores. I wouldn´t accept such a thing with a filesystem
> I trust to hold my data.

Scratch that for now:

I cannot prove that the /home BTRFS is correct as scrubbing it gives
a kernel backtrace I reported on BTRFS kernel mailing list. I recorded
a note in the bug report. The backup went well, so it may not have a
real issue, but until I know feel free to postpone this.

What an irony.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/