search for: mail_fsync

Hiya all, I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on my testbed. The issue is that from what I can see, mail_fsync is set to always : # doveconf -n | grep mail_fs mail_fsync = always The result is that the client does not connect at all, which is not really what I wanted to happen :) Any idea what is going wrong here? Best r...

Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, S?ren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on >> my testbed. The issue is that from what I can see, mail_fsync is set >> to always : >> >> # doveconf -n | grep mail_fs >> mail_fsync = always >> >> The result is that the client does not connect at all, which is not >> really...

This fix is part of next release. ---Aki TuomiDovecot oy -------- Original message --------From: "Juan C. Blanco" <jcblanco at fi.upm.es> Date: 30/05/2018 19:31 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: Fatal: nfs flush requires mail_fsync=always Hello, any news about the attached error? I'm preparing the 2.2 to 2.3 upgrade and having the same error. We have the mail stores in an NFS filer. Regards > On 19.01.2018 11:55, S?ren Skou wrote: >> Hiya all, >> >> I'm seeing this "Fatal: nfs flush requ...

Hi, I need to place a maildir storage on a NFS filesystem, so I set up the config like this: mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always lock_method = dotlock (also tried fcntl - local lockd is running, no success, now using dotlock, to be sure while debugging) The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in mail-index.c is the same) logs a fatal error and quits the session (no daemon crash/coredump). Jan...

...Here are the mount options: > rw,noatime,nodiratime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountvers=3,mountport=1892,mountproto=tcp,local_lock=none > > On the Dovecot side we're running with: > lock_method = dotlock > mail_fsync = never > mail_nfs_index = no > mail_nfs_storage = no > maildir_very_dirty_syncs = yes > mmap_disable = yes > protocol lda { > ? mail_fsync = optimized > } > protocol lmtp { > ? mail_fsync = optimized > } > > Note: we're using Maildir and the usual "work...

Hiya, I'm getting nfs flush requires mail_fsync=always rather consistently from my servers. As you can see below this has been enabled already - So what else am I missing? Best Regards S?ren # 2.3.1.alpha0 (6f9ffa758) [XI:2:2.3.1~alpha0-1~auto+6]: /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1.alpha0 (c9f2afe0) # OS: Linux 4.9.0-4-amd64...

...e? What I have done and results: ssh to server with mailboxes to copy and then su cp /etc/dovecot/dovecot.conf /root/tmp/dovecot_new.conf append text below** to end of dovecot_new.conf try to copy mail 3 different ways (all fail see error messages) doveadm -D -v -c /root/tmp/dovecot_new.conf -o mail_fsync=never sync -1 -u test at propertyzone.co.za pop3c: fail with: Error: Mailbox INBOX.Archive sync: mailbox_set_subscribed failed: Subscriptions not supported doveadm -D -v -c /root/tmp/dovecot_new.conf -o mail_fsync=never sync -u test at propertyzone.co.za pop3c: fail with: Error: Can't create m...

Hello, I've tried to set the above in Dovecot 2.0.3, but according to ktrace (FreeBSD) it still fsync()s a lot (pop3 processes for example). Is this switch useful at all?

....dovecot.org/NFS to see that the settings > make sense. > > Aki > On 14.11.2018 12.00, Adrian M wrote: > > Thank you ! > I was little concerned that the following settings are not in line with > the new version: > > mail_nfs_index = yes > mail_nfs_storage = yes > mail_fsync = always > mailbox_list_index = yes > maildir_stat_dirs = yes > mmap_disable = yes > > > On Wed, Nov 14, 2018 at 10:19 AM Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > >> It should eventually wind down once all the problems are fixed. Of course >> if...

Hello, I followed these steps in http://wiki2.dovecot.org/MailLocation/LocalDisk # Default to no fsyncing mail_fsync = never protocol lda { # Enable fsyncing for LDA mail_fsync = optimized } protocol lmtp { # Enable fsyncing for LMTP mail_fsync = optimized } This gives quite a good performance, but I'm not sure about the risks. Does it mean that things like *put a Sent Mail to Sent folder *change stat...

Hello, I'm deploing a new email cluster using Dovecot over GFS2. Actually I'm using courier over GFS. Actually I'm testing Dovecot with these parameters: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes lock_method = fcntl Are they correct? RedHat GFS support mmap, so is it better to enable it or leave it disabled? The documentation suggest the use of flock. What about it? Thanks, Andrea -- ------------------------------------------------...

Hello, I'm trying to migrate mail accounts from an old server to a new one. As I need to migrate dozens of accounts which take about 1G each, I need to do stateful sync to make my migration in two times : 1 - I run a : doveadm -D -o mail_fsync=never -o imapc_user=user1 at olddomain.fr sync -s "" -R -1 -u user1 at newdomain.fr imapc: > /tmp/firstsync.log 2>&1 my accounts are synced, and I get a "state" string (AQAAAHm4+Jk=) as the output of doveadm sync command. 2 - Changes are made on the old server, and...

...2.12 starting up for imap, pop3, lmtp Jun 4 10:09:20 mail03 dovecot: pop3-login: Login: user=<test at domain>, method=PLAIN, rip=::1, lip=::1, mpid=5540, secured, session=<7x47Jf76IQAAAAAAAAAAAAAAAAAAAAAB> Jun 4 10:09:20 mail03 dovecot: pop3(kiwi at oav.net): Fatal: nfs flush requires mail_fsync=always This is very strange since : # doveconf -n | grep -E 'sync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes So either there is some breakage somewhere or something that is buggy somewhere... Here is my doveconf -n : # 2.2.12: /usr/local/etc/dovecot/dovecot.c...

...rst_valid_gid = 12 > first_valid_uid = 996 > info_log_path = /var/log/dovecot-info.log > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > listen = * > lmtp_save_to_detail_mailbox = yes > log_path = /var/log/dovecot.log > log_timestamp = %Y-%m-%d %H:%M:%S > mail_fsync = never > mail_location = maildir:/var/sentora/vmail/%d/%n > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric > relational regex imap4flags copy include variables body...

Recently updated to 2.2.25. Noticed a migration script I've been previously running fine started giving me the errors below. Remove server doesn't log any failure. doveconf -n attached. + /bin/doveadm -o mail_fsync=never backup -R -u user at domain.com imapc: dsync(user at domain.com): Panic: file mdbox-save.c: line 337: unreached dsync(user at domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d52e) [0x7f58e6da052e] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_ha ndler+0x2a...

...> So many questions ! > > > > > > > > > > > > Aki > > > > > > > > > > > > Thanks for your reply, but both those message are generated from a simple : > > > > > > > > > > > > doveadm -v -o mail_fsync=never backup -R -u foobar at example.com imapc: > > > > > > > > > > > > So I don't know what you mean about dsync service failing ? Surely the DNS lookup succeeded if the 'dsync service' failed due to remote disconnect ? > > > > > >...

...le throughout the years. Here are the mount options: rw,noatime,nodiratime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountvers=3,mountport=1892,mountproto=tcp,local_lock=none On the Dovecot side we're running with: lock_method = dotlock mail_fsync = never mail_nfs_index = no mail_nfs_storage = no maildir_very_dirty_syncs = yes mmap_disable = yes protocol lda { mail_fsync = optimized } protocol lmtp { mail_fsync = optimized } Note: we're using Maildir and the usual "works for me(c), may not work for everyone" applies. -...

...ecot -n # 2.1.15: /etc/dovecot/dovecot.conf # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 base_dir = /var/run/dovecot/ disable_plaintext_auth = no lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mbox_lock_timeout = 15 mins mmap_disable = yes passdb { ? driver = pam } protocols = imap pop3 service anvil { ? client_limit = 203 ? process_limit = 1 } service auth { ? user = r...

Hi there We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community repo) like this: $ doveadm -o mail_fsync=never backup -R -u <username> imapc: For imapc configuration to connect to remote Cyrus server, see below [1]. While this works great for hundreds of mailaccounts, dsync fails with the following error on accounts with @-sign in mailbox names: dsync(<username>): Error: Failed to acce...

On 16.10.2018 21.32, J. de Meijer wrote: > I'm still trying to fix this problem. Hopefully someone can help. > > I've upgraded dovecot to 2.3.3 > # dovecot --version > 2.3.3 (dcead646b) > > That didn't help. > > Next I switched 10-auth.conf to use a local password file (instead of LDAP) Can you provide doveconf -n please? Aki