This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 7 and 8
Revision 7 as of 2011-02-01 12:52:20
Size: 1323
Editor: 230
Revision 8 as of 2011-02-01 13:44:56
Size: 1320
Editor: 230
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
Known bad: ext3 with journal=ordered ? Known bad: ext3 with data=ordered ?

After a loooong thread on the dovecot mailinglist,, Timo finally asked this discussion was taken elsewhere and suggested this wiki-page.


As long as mail_fsync is not set to "never", any (local) filesystem should be equally reliable from data loss issues from dovecot usage. This is because dovecot (and most SMTP-servers) will not aknowledge a message as processed before fsync() returns sucessfully. To quote Timo:

"Success isn't returned to dovecot-lda or IMAP APPEND call until the mail has been fsynced. As long as the disk doesn't lie and the filesystem doesn't lie, there is zero data loss when fsyncing isn't disabled with Dovecot."

What about NFS? Cluster filesystems? Running with mail_fsync=never ?


Dovecot typically runs on Maildirs containing many small files in each directory, and needs high rate of random IOPS. When selecting filesystem for dovecot, one should look for a filesystem that can handle many small files, over filesystems that can efficiently stream large files.

Good candidates: XFS, ext4?

Known bad: ext3 with data=ordered ?

Future ideas

RFC: grouped fsync()

None: FileSystems (last edited 2011-02-02 14:06:16 by 230)