https://bugs.kde.org/show_bug.cgi?id=332013
Daniel Vrátil <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #11 from Daniel Vrátil <[email protected]> --- The "The file is too large" error is not from the database, but is returned by the system when we try to save content of the item on disk. Because a new file is being created (O_WRONLY|O_CREAT|O_TRUNC), I doubt that the problem is the actual size of the file. Instead the problem could be in the size of the directory, or rather in the amount of files in the directory. Some filesystems have a limit on maximum amount of files in a directory, in your case this can be either a limitation of NFS or the underlaying file system. I'd be interested in seeing output from ls -1 ~/.local/share/akonadi/file_db_data | wc -l I still agree with what Christian said: NFS is currently not a supported use case at the moment (which can change in the future, however). People were successful running Akonadi on NFS (using either SQLite or external DB server), but the access to external payloads will still be slow. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
