similar to: Corrupt index files

On 21.07.2017 20:47, Bruce Guenter wrote: > I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with > Maildir storage. This has worked well for most of the accounts for > several months. > > However in the last couple of weeks we are seeing increasing errors > regarding corrupted index files. Some of the accounts affected are > unable to retrieve messages due to

Am 21.07.2017 um 19:47 schrieb Bruce Guenter: > > I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with > Maildir storage. This has worked well for most of the accounts for > several months. > > However in the last couple of weeks we are seeing increasing errors > regarding corrupted index files. you should avoid this one solution is to use loadbalancers

On Mon, Jul 24, 2017 at 07:56:23PM +0300, Aki Tuomi wrote: > Well, dovecot does not really guarantee access concurrency safety if you access indexes using more than one instance of dovecot at the same time. Pardon my ignorance, but how does Dovecot handle when an IMAP client connects multiple times concurrently? Does it not launch multiple instances? > Nevertheless, did you try w/o

On Mon, Jul 24, 2017 at 08:39:36AM +0300, Aki Tuomi wrote: > Do you have users accessing the files concurrently from more than one > dovecot instance at a time? Yes. Apparently it is fairly common behavior for some IMAP clients to open up multiple connections to the same mailbox. Some times the multiple accesses came from different servers (stand alone IMAP client and a webmail system), but

Hi, I'm experiencing a problem I need some pointers to debug. I'm running Dovecot 2.0.15 and have a client which keeps causing log-entries like: Nov 4 15:10:42 mail dovecot: imap (test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: indexid changed 1320419300 -> 1320419441 (sync_offset=0) Nov 4 15:10:42 mail dovecot:

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) It was

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. NFS may have been used. Panic: IMAP(user): file mail-index-sync-update.c: line 843 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- >indexid || map->hdr.indexid == 0) Two different backtraces to this error are: 0 libSystem.B.dylib 0x00007fff87b775ea __kill + 10 1

Hello, I'm introducing to you the decentralized cloud Cherrypop. Combining libvirt and LizardFS (as of now) it becomes a cloud completely without masters. Thus, any node is sufficient for the cloud to be up and therefore no wasted resources and no single point of failure. It's still pretty crude software but will work with some tinkering. Hope you try it and like it! For more

I got the following panic on 1.2.3: Panic: file mail-transaction-log-append.c: line 88 (log_buffer_move_to_memory): assertion failed: (file->buffer_offset + file->buffer->used == file->sync_offset) It's probably related to the file system holding the indexes being full.

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed

Hi - We tried to access a dovecot-0.99.10.7 IMAPS server with a Blackberry 7230. The Blackberry was on loan so we don't have much access to it for testing. We got the following in our logs: Jul 27 12:30:27 xserv imap-login: Login: testuser [xxx.xxx.xxx.xxx] Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree file /home/testuser/mail//.imap/INBOX/.imap.index.tree Jul 27

Should I be concerned about these errors? imap(msun): Jun 13 13:21:38 Error: Error indexing mbox file /home/msun/mail/Deleted Messages: LF not found where expected imap(msun): Jun 13 13:39:08 Error: Corrupted binary tree for index /home/msun/mail/.imap/INBOX/.imap.index: lookup returned index outside range (1 >= 0) imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file

http://dovecot.org/test/ - Added pop3_mails_keep_recent setting. Currently this only means that mails won't be moved from new/ to cur/ in maildir. More I/O friendly. - Fixed \Recent-flag handling and counters to work correctly with maildir. I think it's finally working right :) - mbox syncing fixes (but expunging still not implemented) - some other fixes.. Please try and report what

Hi Timo and All, after upgrading to 2.1.2 i'm getting a lot of these messages: Error: Corrupted squat uidlist file XXXXXX wrong indexid I did not have them before. Ideas? Luca

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200

We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using mboxes, mostly without issues. However I had to trash the index/cache files (too many folders were showing corruption issues which is especially bad for Prayer Webmail ".prayer" folders that store preferences; Prayer sees a disconnection as the folder being missing!). I've had one imap process panic in mailbox

Anyone made some performance comparison between XFS and ZFS with ZIL on SSD, in gluster environment ? I've tried to compare both on another SDS (LizardFS) and I haven't seen any tangible performance improvement. Is gluster different ?

Two nights ago I took a leap and extended my testing of dovecot 1.1 by replacing 1.0 for the approx 15 users I had on 1.0. At that time I also for the first time tried dovecot 1.1 in a load balanced 2 server configuration with indexes on NFS. I was hoping I did this right, using the mail_nfs params and 1.1 so fchown etc would flush the access cache, but I am getting a number of messages and

(I will not make a joke about the streets of Carlyle) Jan 13 19:09:07 mail dovecot: lda(john at example.com): Panic: file mail-transaction-log-file.c: line 1148 (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <= file->sync_offset) Jan 13 19:09:08 mail kernel: pid 8435 (dovecot-lda), uid 89: exited on signal 6 (core dumped) Jan 13 19:14:16 mail dovecot: lda(john

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, 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