On Tue, Aug 01, 2017 at 01:14:10PM +0300, Sami Ketola wrote:
Each imap connection is one imap process. So if (unlimited) thunderbird connects to dovecot imap and sees 30 folders, it will open 30 imap connections and dovecot will launch imap process to manage each connection. And on top of that LMTP delivery again is another process to access the FS.
That is what I expected, yes.
If these processes get different view of the filesystem you will face corruption. Specially when you are dealing with multiple servers the metadata syncing across servers is a challenge for the cluster filesystems.
Of course. It can be managed, but still best avoid it by using a director. We had been using a load balancer that persistently mapped remote IPs to one server or another, but discovered that was not sufficient (clients using both webmail and a desktop client came in from different remote IPs, oops), so we implemented the Dovecot director on our load balancer.
I’m a bit surprised that the corruption does happen even with one server.
That is what I am seeing. Even when the account is accessing the maildir from a single server, there is still corruption.
Without testing I still would say that it’s LizardFS to blame. There was similar problems with another cluster filesystem GlusterFS too.
Is there anything I could test to diagnose this further? I have moved the account with the most frequent problems to physical storage, but this won't tell me why LizardFS is causing problems.
-- Bruce Guenter <bruce@untroubled.org> http://untroubled.org/