dovecot - Oct 2004 - Filesystem requirements

What are the filesystem requirements for dovecot - for example I see
some people are running with atime updates switched off (as I intend to
do so myself), so presumably dovecot has no need of an accurate atime
implementation.

How about directory atime?  ctime/mtime etc?

I'm intending to run on a linux box using local disk, so am currently
considering using reiserfs (3.6) with noatime, nodiratime options since
that appeared to work with good performance on the quick benchmark test
I tried.  I do not have a particularly high opinion of reiserfs
reliability, but it normally appears to fail in a all-or-nothing way (ie
filesystem unusable) rather than some files going corrupt or missing, so
I can work round that with a backup regime.

	Nigel.
-- 
[ Nigel Metheringham           Nigel.Metheringham at InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]

On 26.10.2004, at 14:54, Nigel Metheringham wrote:
> What are the filesystem requirements for dovecot - for example I see
> some people are running with atime updates switched off (as I intend to
> do so myself), so presumably dovecot has no need of an accurate atime
> implementation.
>
> How about directory atime?  ctime/mtime etc?
Only place where atime is used is when listing mboxes. If atime < 
mtime, the mailbox is returned with \Marked flag. It might be of a 
small optimization for some clients, but not very important.

ctime is checked with dotlocks, but mtime is as well.

mtime is used in a lot of places and it should be accurate. For both 
directories and files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20041101/ff29e9b7/attachment-0001.bin>