rmdir() EBUSY warnings on 2.2.12

[Giel van Schijndel]

On Fri, Jul 04, 2014 at 01:59:02 +0300, Timo Sirainen wrote:
> On 4.7.2014, at 1.30, Giel van Schijndel <giel+dovecot at mortis.eu> wrote:
> 
>> I'm getting a lot of syslog spam on FreeBSD 10 from
>> nfs_flush_file_handle_cache_dir where, apparently it tries to rmdir()
>> the mountpoint of my mail storage.
>> 
>>> Jul  4 00:04:44 mailhost dovecot: imap(user at example.com): Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail/vhosts/example.com) failed: Device busy
>> 
>> We're using ZFS and have /var, /var/mail, /var/mail/vhosts,
>> /var/mail/vhosts/example.com and /var/mail/vhosts/example.com/user as
>> separate ZFS datasets (to enable per-user and per-domain snapshotting).
>> 
>> So apart from NFS flushing being unnecessary (ZFS != NFS) I'm not really
>> sure why using rmdir() for another directory than the Maildir specified
>> in mail_location is a good idea. I.e. given that Maildirs shouldn't ever
>> be emtpy (cur,new,tmp) anyway.
> 
> Don't set mail_nfs_index=yes or mail_nfs_storage=yes and Dovecot won't
> try these kludgy things to flush NFS caches. They don't fully work
> anyway and they are highly discouraged for any kind of use, ever.
> Mainly they exist for backwards compatibility.

1. Aren't those the defaults? Because I didn't set these options.
2. I've just explicitly set both to 'no' and I'm still seeing these errors.

-- 
Met vriendelijke groet,
With kind regards,
Giel van Schijndel
--
"For a successful technology, reality must take precedence over public
 relations, for nature cannot be fooled."
  -- Richard Feynman
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://dovecot.org/pipermail/dovecot/attachments/20140704/116f9668/attachment-0001.sig>