physical storage, but
this won't tell me why LizardFS is causing problems.
--
Bruce Guenter http://untroubled.org/
signature.asc
Description: Digital signature
or front
end (instead of just a semi-persistent load balancer), the instances
have been reduced, but it is still happening on accounts that are not
being accessed across multiple servers. I will see if I can pin these
down to a single server and move them onto non-shared storage there.
--
B
es the
multiple accesses came from different servers (stand alone IMAP client
and a webmail system), but there is corruption even when all the
accesses are going through the same server.
(Yes, we need a director. I am working on integrating that into our network.)
--
Bruce Guenter
On Fri, Jul 21, 2017 at 03:25:39PM -0600, Bruce Guenter wrote:
> We had been using a loadbalancer with persistence to reduce the
> problems, and today I switched to everything running on a single box to
> avoid any cross-node contention. Unfortunately, the problem still
> happens, ev
ith optimize settings
> to i.e
>
> mail_fsync = always
> mmap_disable = yes
I have those, but...
> mail_nfs_storage = yes
> mail_nfs_index = yes
I missed seeing those.
Thanks
--
Bruce Guenter http://untroubled.org/
signature.asc
Description: Digital signature
I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with
Maildir storage. This has worked well for most of the accounts for
several months.
However in the last couple of weeks we are seeing increasing errors
regarding corrupted index files. Some of the accounts affected are
unable t
