On Fri, Jul 21, 2017 at 08:50:16PM +0200, Robert Schetterer wrote:> you should avoid this > one solution is to use loadbalancers with persistanceWe 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, even when they were all running imap on a single box. We are moving to a director type setup instead of a persistent load balancer to eliminate the last source of cross-node access.> i think you could rare the corrupt > with optimize settings > to i.e > > mail_fsync = always > mmap_disable = yesI have those, but...> mail_nfs_storage = yes > mail_nfs_index = yesI missed seeing those. Thanks -- Bruce Guenter <bruce at untroubled.org> http://untroubled.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20170721/c85d3bd2/attachment.sig>
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, even when they were all running imap on a single box.I just confirmed this. One of the mailboxes was deleted and recreated from scratch, and since recreation it has only been accessed on a single box. It *still* is having corrupt index problems. This is not just caused by accessing the mailboxes on different servers. -- Bruce Guenter <bruce at untroubled.org> http://untroubled.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20170721/5bc19d63/attachment.sig>
Am 21.07.2017 um 23:58 schrieb 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, even when they were all running imap on a single box. > > I just confirmed this. One of the mailboxes was deleted and recreated > from scratch, and since recreation it has only been accessed on a single > box. It *still* is having corrupt index problems. > > This is not just caused by accessing the mailboxes on different servers. >there may exist additional problems, but do you moved away from cluster filesystem too, switching back related parameters ? On a single box with local storage you shouldnt have a problem unless there are hardware failures or other broken config settings, again rethink your whole setup, if you in production and afraid brake something in total, you should call paid guru support Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schlei?heimer Stra?e 26/MG, 80333 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein