Fixed: http://hg.dovecot.org/dovecot-2.2/rev/9b53f6bf0427

But you shouldn't use mail_nfs_*=yes settings in any case. If you use multiple Dovecot servers, you should use Dovecot director and then you can keep using mail_nfs_*=no. If you use only a single Dovecot server then mail_nfs_*=no works fine also.

On 17.4.2014, at 18.37, Wesley Huang <huang@utsc.utoronto.ca> wrote:

Hi All,

I was able to find some time and investigate further. The culprit has been found: "mailbox_list_index=yes". We'd like to use the IMAP NOTIFY extension and this option is a must. But turning on mailbox_list_index with index stored on NFS mounts caused the the error I reported.

Is it a designed/known behaviour or it is a bug? Hopefully my email will be caught maintainers' eyes.

Cheers,

Wesley

On 14-04-11 01:41 PM, Wesley Huang wrote:

...

Hi Alessio,

After days sorting the Heartbleed mess, I managed to set up Debian Squeeze amd64 for the test and I'm seeing the same error message:

Fatal: nfs flush requires mail_fsync=always

doveconf -n | egrep 'fsync|nfs'

mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes

Cheers,

Wesley

On 14-04-03 09:24 AM, Alessio Cecchi wrote:

...

Hi,

I'm using Maildir on Debian 6 64bit, try to "grep" for "fsync" on all configuration files.

Try also to install the same dovecot+configuration on Debian 6.

Let me know! Ciao

Il 03/04/2014 15:12, Wesley Huang ha scritto:

...

Hi Alessio,

I have 2.2.12 installed in Debian Wheezy amd64 server. mail_fsync is specified and detected. Are you using mbox or maildir or dbox? We're using mbox and seeing the error.

dovecot --version

2.2.12

dovecot -n | grep -E 'sync|nfs'

mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes

egrep 'nfs|fsync' 10-mail.conf | egrep -v '#'

mail_fsync=always mail_nfs_storage = yes mail_nfs_index = yes

uname -r

3.2.0-4-amd64

Cheers,

Wesley

On 14-04-03 04:22 AM, Alessio Cecchi wrote:

...

Il 08/01/2014 09:23, Troton_admin ha scritto:

...

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).

Hi,

I have a similar configuration but with dovecot 2.2.12 and NFS for me works fine. Have you insert the "mail_fsync = always" in the right place? Is there only one "mail_fsync" setting in your config? First check this:

root@mx:/etc/dovecot# grep mail_fsync /etc/dovecot/ -R conf.d/10-mail.conf:mail_fsync = always

root@mx:/etc/dovecot# dovecot -n | grep -E 'sync|nfs' mail_fsync = always mail_nfs_index = yes mail_nfs_storage = yes maildir_very_dirty_syncs = yes

2.2.12: /etc/dovecot/dovecot.conf

OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.9

Let me know. Ciao