Bug 300819 - Fontend not reporting full filesystem for akonadi/file_db_data (resulting in Sync hangs)
Summary: Fontend not reporting full filesystem for akonadi/file_db_data (resulting in ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: KDE PIM Mobile
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Meego/Harmattan Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 15:49 UTC by Bernhard E. Reiter
Modified: 2016-09-29 07:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard E. Reiter 2012-05-29 15:49:12 UTC
When online with the GPRS or UTMS connection, folder syncs
very soon hang, so they stay at a random percentange and don't move anymore.
This situation occurs for all syncs in larger folders, when using the mobile connection.
It does not occur with the WLAN connection.

Switching to offline and then to online again usually changes the sync percentage
to something lower and hangs there. Closing the Kontact Touch Mail frontend
and reopening it does not help.

Version installed:
ii  kmail-mobile                             4:4.9~.20120521.git084e17ba-1maemo6.6  
ii  kdepimlibs-kio-plugins                   4:4.9~20120521.git9360eadef-maemo6.6 
ii  kdepim-runtime                           4:4.8+20120521.git8ce8c5b0-1maemo6.2 
ii  akonadi-server                           1.6.50.20120516.gitdeec1f-1maemo6.2 

I've also notived the issue with previous revision.
When using the same N9 and its internet connection via an ideapad with Kontact Touch,
there is no hang.

So maybe the N9 does something special when it is using the mobile internet connection?
Comment 1 Bernhard E. Reiter 2012-06-04 07:54:19 UTC
Meanwhile I also observed a similiar hang on a WLAN connection.
So it does not depend on the "mobile (UTMS / GPRS)" connection status
and I've broadened the subject.

Andre, maybe the akonadi-server version does make a difference, at least
the NEWS file of 1.6.90 lists something about "- Update agent interface to include collectionTreeSynchronized signal." and I'm not sure if 1.6.50 has this already or if it is related at all.
Comment 2 Andre Heinecke 2012-06-05 16:25:26 UTC
I've updated the available akonadi server version, but so far i am unable to reproduce this bug.
Could you please do a full shutdown and then obtain the debug output from starting kmail-mobile on the command line.
The recent output around such a hang of /var/log/syslog would also be helpful.
Comment 3 Bernhard E. Reiter 2012-06-06 12:28:42 UTC
Also updated to akonadi
Version: 1.7.50.20120604.gitdeec1f8deec1f-1maemo6.3

it turned out this was a problem related to the filesystem.
I have synced a rather large account and thus I've moved the akonadi data store
too the MyDocs partition which is vfat and larger as outlined in
http://userbase.kde.org/Kontact_Touch/Harmattan#Additional_Notes

While there is still space on the partition  the error message by akonadi is:
Insert: payload file  "/home/user/.local/share//akonadi/file_db_data/141229_r0"  could not be open for writing!  Error:  "No space left on device"  

Turns out there are already a large number of files in that directory:
ls|wc                                                                           
    32764
and there is a limit
~/MyDocs/akonadi/file_db_data $  touch x                                        
touch: x: No space left on device     

So the workaround seems to be that I need to tune akonadi to create less
files in that directory. Which would have been okay. if the error message would have reached me as a user. 

So I am refocussing this issuse towards:
Problem description: A filesystem problem (cannot create new files) must be reported to the user by the frontend.
Current behaviour: A sync hang which is not recoverable.
Rationale: The effects of the defect are severe, as the client get unusable. Filesystem issues can appear under normal usage and the user may be able to recover from the situation by other means if informed. E.g. the user may be able to remove some folders within Kontact or make space on the used filesystem by other means.