search for: mmap_disable

I wasted too much time today doing this, but they do show a few interesting things: 1) mmap_disable=yes is faster than mmap_disable=no. I didn't expect this. I'm not yet sure why this is, but possibly because then it updates the mail index by reading the changes from dovecot.index.log, instead of reopening and re-mmaping dovecot.index. At least that's the biggest difference between th...

Greetings, On http://wiki.dovecot.org/MainConfig I read: "mmap_disable = no Don't use mmap() at all. This is required if you store indexes to shared filesystems (NFS or clustered filesystem). " Does that mean: 1. mmap is required when using NFS or 2. it is required to don't use mmap at all when using NFS? Sorry if this is obvious. Best regards....

...dn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0: Maildir, dovecot-1.0 hg + inotify dotlock wait patch, mmap_disable=yes v1.1: Maildir, dovecot hg, mmap_disable=no cydir: Cydir, dovecot hg, mmap_disable=no 1 client -------- ./imaptest logout=0 seed=1 secs=10 clients=1 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30%...

Version: 1.0test53 .. 1.0.rc14 (ie. all 1.0alpha, 1.0beta and 1.0rc versions so far). 0.99.x versions are safe (they don't even have mmap_disable setting). Problem: When mmap_disable=yes setting is used, dovecot.index.cache file is read to memory using "file cache" code. It contains a "mapped pages" bitmask buffer. In some conditions when updating the buffer it allocates one byte too little. Exploitability: I think it...

Version: 1.0test53 .. 1.0.rc14 (ie. all 1.0alpha, 1.0beta and 1.0rc versions so far). 0.99.x versions are safe (they don't even have mmap_disable setting). Problem: When mmap_disable=yes setting is used, dovecot.index.cache file is read to memory using "file cache" code. It contains a "mapped pages" bitmask buffer. In some conditions when updating the buffer it allocates one byte too little. Exploitability: I think it...

Hi all, I'm experimenting with having the mail store on a 9p file system that lacks mmap() functionality. So I disabled it in dovecot: mmap_disable = yes However, I keep getting the following error messages in my log: Oct 15 16:55:00 computer-name dovecot: imap user at domain.com[192.168.1.3] Error: mmap() failed with file /mail/mailboxes/domain.com/user/indexpvt-accounts/other-user/mailboxes/INBOX/dovecot.index.pvt.log: Invalid argument I onl...

...ackend as if they were on a NFS like setup but this seems not to work at least on GFS2 on rhel 6.1. We have a two node cluster sharing two GFS2 filesystem - Index GFS2 filesystem to store users indexes - Mailbox data on a GFS2 filesystem The specific configs for NFS or cluster filesystem we used: mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes fsync_disable=no lock_method = fcntl mail location : mail_location = mdbox:/var/vmail/%d/%3n/%n/mdbox:INDEX=/var/indexes/%d/%3n/%n But this seems not to work for GFS2 even doing user node persistence, maillog is plagged of err...

...Alpha3 running on x86_64 Linux 2.6 multi-CPU box using Maildir folders. Moving messages from one folder to another in Thunderbird 1.0.7, regardless of their size (usually small), produced error 83, "Out of memory", when both of these parameters were unset (default): mail_read_mmaped, mmap_disable. The log line before the error was pool_system_malloc(): Out of memory. I initially changed mmap_disable to "yes", the error stopped, but it still wasn't moving messages reliably. I then set MM parameters more aggressively: mail_read_mmaped = yes, mmap_disable = no (and the third...

...ttp://wiki2.dovecot.org/NFS, but in the new ones I have a director proxy directing all connections from each user to the same server (I don't specify any server for the user, director selects it according to the hash algorithm it has). Some doubts I have for the recommended in that url: * mmap_disable: both single and multi server configurations have mmap_disable=yes but in index file section says that you need it if you have your index files stored in nfs. I have it stored locally. Do I need mmap_disable=yes? What it's the best? * dotlock_use_excl: it is set to no in both configurations,...

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

http://dovecot.org/test/ - vpopmail authentication fix - many mmap_disable=yes fixes and a few optimizations - pop3 hang fix - mbox fix for "last-uid lost" error (hopefully last one) - mbox fix for losing dirty flag, causing lost message flags mmap_disable=yes seems to be finally working pretty well. There should be no more cache file related errors with it...

Hello all, We are facing extremely slow GFS2 issues in Redhat 7 64 bit. Backend is 16 Gbps FC SAN so no issues there. I have scoured the entire (anyways most of the) Internet and arrived at the following settings. mmap_disable = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes mmap_disable = yes lock_method = fcntl Did a systemctl restart dovecot and did not find any major improvement. Can you please help. Regards Durga Prasad --- This email has been checked for viruses by Avast antivirus software....

Hi all, I've a little pb with 1.0-stable on nfs share without lockd : with : - lock_method = dotlock - mmap_disable = yes I've : - dovecot: Jul 22 11:58:33 Error: IMAP(xxxxxxxx): open() failed with index file (null): Bad address with : - lock_method = dotlock - mmap_disable = no I've : - dovecot: Jul 22 11:59:47 Error: IMAP(xxxxxxxx): lock_method=dotlock and mmap_disable=no combination isn'...

..., file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes to work without reading the main index file more than once. Are maildir syncing problems finally fixed now? :) I think the "message sequence out of range" problems are fixed now too. Rest of the important known problems are mostly related to mmap_disable=yes or fcntl_locks_disa...

...text search indexes for SEARCH BODY/TEXT, but I didn't benchmark these now. It looks like CVS HEAD is quite a lot faster than v1.0. I think that's mostly because of the APPEND optimization. Here are the results: 100MB ext3 filesystem inside a file in XFS. C: CVS HEAD, fsync_disable=yes, mmap_disable=yes S: CVS branch_1_0 (upcoming 1.0.rc28), fsync_disable=yes, mmap_disable=yes ./imaptest seed=1 secs=60 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo C: 11275 5647 5597 11275 11264 16179 5571 4126 11256 6074 22531 C: 11287 5740 5606 11287 11275 16193 5698 4154 11267 6064 22553...

dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I. -Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox -DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a imaptest.c: In client_append function: imaptest.c:1492: error: too many arguments for i_stream_create_limit function

...ethod = 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 = root } service imap-login { ? chroot = login ? client_limit = 10 ? user = dovecot ? vsz_limit = 256 M } service pop3-login { ? chroot = login ? client_l...

...if imap connections are round-robined between imap servers? I've seen various people using different actimeo settings, some set at 0, some slightly higher - as much as 30. Can anyone speak on experience they have had with netapps on this subject? The following sound like they are required: mmap_disable=yes lock_method=dotlock Has anyone been successful with fnctl() on netapps with dovecot? Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://dovecot.org/pipermail/dovecot/attachments/20060613/eff9d8b8/attachment.html

...remove indexes like: find /var/dovecot_indexes/home/ -name 'dovecot*' -type f -delete but this is not good solution What am I doing wrong ? For tunning nfs in 10-mail.conf: --------- "mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h namespace inbox { ? inbox = yes } mmap_disable = yes dotlock_use_excl = no mail_fsync = always mail_nfs_storage = no mail_nfs_index = no lock_method = fcntl mail_temp_dir = /tmp mail_plugins = quota expire notify mail_log mailbox_idle_check_interval = 30 secs mail_temp_scan_interval = 1w maildir_very_dirty_syncs = no ------------- doveconf...

How can I configure the dovecot for working with maildir's through NFS? If I add option "index_mmap_invalidate = yes" (as in doc/nfs.t) then in log I have this message: "Error: Error in configuration file /etc/dovecot.conf line 296: Unknown setting: index_mmap_invalidate" If I try to get the mail without option "index_mmap_invalidate" then I have in log this