search for: mail_index_write

...td=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT mail-index-write.o -MD -MP -MF .deps/mail-index-write.Tpo -c -o mail-index-write.o mail-index-write.c mail-index-write.c: In function 'mail_index_write': mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' *** Error code 1 Stop in /opt1/source/dovecot-1.1.rc6/src/lib-index. *** Error code 1 Stop in /opt1/source/do...

...;)<6812><gn4yobOMJlW5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL2>/dovecot.list.index.log: duplicate transaction log sequence (2) Jul 02 16:33:35 Panic: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: file mail-index-write.c: line 137 (mail_index_write): assertion failed: (file->hdr.prev_file_seq == hdr->log_file_seq) Jul 02 16:33:35 Fatal: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: master: service(imap): child 6812 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap...

...so.0 [0x7f03e16ff8aa] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f03e16ffc53] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x7f03e1bce244] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_try_lock_exclusive+0x20) [0x7f03e1bce2d0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_write+0x31d) [0x7f03e1be287d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x166) [0x7f03e1bda3d6] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0x7f03e1ba1d16] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_transaction_save_commit_pre+0x4d2) [0x7f03e1b9d0b2] -> /usr...

...ansaction_log_close+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) [0x7feb8a322eab] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) [0x7feb8a31a231] ->...

...transaction_log_close+0x34) [0x7f25fc9e6f04] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_transaction_log_move_to_memory+0xed) [0x7f25fc9e709d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0x60) [0x7f25fc9e10b0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_write+0x1e1) [0x7f25fc9df3a1] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0x68a) [0x7f25fc9ca13a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x5b0) [0x7f25fc9d4090] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x13b) [0x7f25fc9cc1eb] ->...

...and dovecot.index.log files (without dovecot.index.cache)? They shouldn't contain anything sensitive (only message flags). Tested with the index files you sent. It gets fixed automatically in my tests. The backtrace shows that after fsck it fails to write the fixed index to the disk, because mail_index_write() fails for some reason. Except there's no error logged about it, which is rather weird. Do you still have the lmtp core? Could you do: fr 9 p *log.index -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/201...

...e+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- >> storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- >> storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) >> [0x7feb8a322eab] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) [0x7feb8a31a2...

Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the

Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the

...7f30) [0x7f77b9f85f30] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f77b9f85f9a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f77b9f39515] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc296f) [0x7f77ba2b996f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_write+0x1be) [0x7f77ba2b8c3e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x262) [0x7f77ba2b1012] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_atomic_finish+0x26) [0x7f77ba225a36] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x61) [0x7f77ba229d91]...

...;6812><gn4yobOMJlW5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL2>/dovecot.list.index.log: duplicate transaction log sequence (2) > Jul 02 16:33:35 Panic: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: file mail-index-write.c: line 137 (mail_index_write): assertion failed: (file->hdr.prev_file_seq == hdr->log_file_seq) > Jul 02 16:33:35 Fatal: imap(<REMOVED_EMAIL2>)<6812><gn4yobOMJlW5D+Vb>: master: service(imap): child 6812 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service...

...99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad- function-cast -Wstrict-aliasing=2 -MT mail-index-write.o -MD -MP - MF .deps/mail-index-write.Tpo -c -o mail-index-write.o mail-index- write.c mail-index-write.c: In function 'mail_index_write': mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' mail-index-write.c:179: error: 'struct stat' has no member named 'st_ctim' make[3]: *** [mail-index-write.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive]...

..._transaction_log_sync_lock -> mail_transaction_log_lock_head -> mail_transaction_log_file_lock -> mail_index_lock_fd -> file_wait_lock -> file_lock_do "Inner" write lock: maildir_transaction_save_commit_pre -> maildir_sync_index_finish -> mail_index_sync_commit -> mail_index_write -> mail_transaction_log_rotate -> mail_transaction_log_file_create -> mail_transaction_log_file_create2 -> mail_transaction_log_file_lock -> mail_index_lock_fd -> file_wait_lock -> file_lock_do The file being locked is the same, dovecot.index.log. In another case, maildir_syn...

...x7f27cef8b19a] -> /usr/lib64/dovecot/libdovecot.so.0(i_syslog_fatal_handler+0x33) [0x7f27cef8b253] -> /usr/lib64/dovecot/libdovecot.so.0(+0x24b1a) [0x7f27cef3cb1a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xd3965) [0x7f27cf2ce965] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_write+0x1f5) [0x7f27cf2cd7a5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x2c4) [0x7f27cf2c5214] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x510e8) [0x7f27cf24c0e8] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_transaction_save_commit_pre+0x40f) [0x7f...

...ovecot.index.cache)? They shouldn't contain anything sensitive (only >> message flags). > > Tested with the index files you sent. It gets fixed automatically in my > tests. > > The backtrace shows that after fsck it fails to write the fixed index to > the disk, because?mail_index_write() fails for some reason. Except > there's no error logged about it, which is rather weird. Do you still > have the lmtp core? Could you do: > > fr 9 > p *log.index (gdb) f 9 #9 0x00007f25fc9e709d in mail_transaction_log_move_to_memory (log=0x55e3e2b81eb0) at mail-transaction-l...

...log_close+0x30) [0x7feb8a336230] -> /usr/lib64/dovecot/libdovecot- > storage.so.0(mail_transaction_log_move_to_memory+0xd5) [0x7feb8a3363e5] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_move_to_memory+0xa0) [0x7feb8a330440] -> /usr/lib64/dovecot/libdovecot- > storage.so.0(mail_index_write+0x183) [0x7feb8a32e9d3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_fsck+0xc1f) [0x7feb8a3186ff] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x49b) > [0x7feb8a322eab] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) [0x7feb8a31a231]...

...1a) [0x7f8f2aca4e1a] -> /usr/lib/ dovecot/libdovecot.so.0(i_syslog_fatal_handler+0x33) [0x7f8f2aca4ee3] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f8f2ac562bf] -> /usr/lib/dovecot/lib dovecot-storage.so.0(+0xd6fc5) [0x7f8f2afe5fc5] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_write+0x1f5) [0x7f8f2afe4e15] -> /usr/lib/dovecot/libd ovecot-storage.so.0(mail_index_sync_commit+0x2c4) [0x7f8f2afdc854] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x55b08) [0x7f8f2af64b08] -> /usr/lib/dovecot /libdovecot-storage.so.0(maildir_transaction_save_commit_pre+0x40f) [0x7f8f2af5...

...ovecot/libdo vecot.so.0(default_fatal_handler+0x2a) [0x7fe817a9819a] -> /home/mail/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe817a4a335] -> /home/mail/dovecot/lib/dovecot/ libdovecot-storage.so.0(+0xd499f) [0x7fe817ddb99f] -> /home/mail/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_index_write+0x1e6) [0x7fe817ddac46] -> /home/mail/dove cot/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x2db) [0x7fe817dd2f2b] -> /home/mail/dovecot/lib/dovecot/libdovecot-storage.so.0(imapc_mailbox_sync_init +0x20d) [0x7fe817d7690d] -> /home/mail/dovecot/lib/dovecot/libdovecot-storage....