similar to: readdir and rename don't mix; patch included

I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108

Program terminated with signal 6 GNU gdb (GDB) 7.0-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was

For quite some time I have seen dovecot imap exit with a sig11 without any other error message, but usually with the frequency of between once per week and once per day (per server). A few weeks ago I finally enabled core dumping with debug symbols and it seemed to happen less often. I finally caught a coredump that wasn't overwritten. I have no idea what on the client end may cause it,

Log: Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): /home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216 -> 2) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap [0x80efdb1]

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

https://bugzilla.samba.org/show_bug.cgi?id=5802 Summary: misleading error message in atomic rsync Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: normalperson@yhbt.net

Hi Gents, I have written a backup script with rsync, which is working fine for a long time. Now a problem has occured. which I am not able to solve by my own: Before I am doing the backup I am checkig if there are any changes to backup ... rsync --delete $RSYNC_EXCLUDE -avzne "$RSYNC_SSH" $RSYNC_SOURCE $RSYNC_DESTINATION But when I have created a path of new directories in

Hi, I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur in maildir-sync.c::maildir_scan_dir without adding an info part. On the page http://cr.yp.to/proto/maildir.html is written that mails have to be renamed to uniq:info when moved to the cur directory. Could this be a bug in dovecot? --

In the log: Dec 1 17:24:00 postamt dovecot: IMAP(scxxxxx): /home/s/c/scxxxxx/Maildir/dovecot-uidlist: Duplicate file entry at line 1: 1259679049.M329485P1617.postamt.charite.de,S=142073,W=143959:2,Sb (uid 3157 -> 3159) Dec 1 17:24:00 postamt dovecot: IMAP(scxxxxx): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 1 17:24:00

Between versions 1.0.4 and 1.0.5 there were some changes to the way dovecot-shared group ownership is propogated into new maildirs. Changing the group of new_dir/{tmp,new,cur} was added, but changing the group of new_dir itself was removed. As far as I can tell, this latter change may have been accidental. This patch puts the functionality back, in the 1.1 tree.

I have inconsistent directory listing on share mounted on linux from windows 2k. Some time not all files appear in the directory listing. If reading directory listing multiple times (60-200 times) files listed originally would have one or two files missing in one of consecutive lists. The same problem appear as well if you are making backup of Windows files from multiple directories, there are

ok, so this is not entirely an rsync question. but, it seems the 'crowd' most familiar w/ hard-linking are the rsync crowd. so ... i'm doing rsync + incremental backups to a local drive. the incremental steps, currently, use the rsync REMOTE_DIR OLD_DIR ... time passes ... cp -al OLD_DIR NEW_DIR rsync REMOTE_DIR NEW_DIR approach. all works great. i'd *like* to be

https://bugzilla.mindrot.org/show_bug.cgi?id=1768 Jakub Jelen <jjelen at redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jjelen at redhat.com --- Comment #2 from Jakub Jelen <jjelen at redhat.com> --- Created attachment 2523

Dovecot's transactions often write-lock dovecot.index.log twice (without unlocking in between), and then unlock it twice. Is that intended, or is that a bug? If I read the man pages correctly, double write-locking is pointless but safe. But double unlocking could cause data corruption during the period between the first and second unlocks, because the locks don't nest (are not

When playing with large numbers of IMAP keywords on dovecot-1.2.6 imap crashed: Panic: pool_data_stack_realloc(): stack frame changed Looks like either maildir_file_do() shouldn't T_BEGIN/T_END or the keywords array should start larger. 0 libSystem.B.dylib 0x00007fff875f4eba __kill + 10 1 libSystem.B.dylib 0x00007fff875f4eac kill + 14 2 libSystem.B.dylib

Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c

Hi, Arthur found out that ext3 is not changing the ctime on the "old_dir" (the object that is being renamed), but ext2 does. It looks to me like this is simply an omission of the following little patch from namei.c - Peter - --- fs/ext3/namei.c.orig Mon Mar 19 22:55:03 2001 +++ fs/ext3/namei.c Mon Mar 19 22:53:40 2001 @@ -985,6 +985,13 @@ new_dir->i_version =

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. Pretty sure NFS was not used. Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: seq_range_exists(&ibox->recent_flags, uid) The backtrace is: 0 libSystem.B.dylib 0x00007fff85025166 __kill + 10 1 libSystem.B.dylib 0x00007fff850a80e0

Dovecot-1.1.15 assert-fails frequently. Attached are some errors from the logs, and a stack trace from the common panic. Hope you can fix these soon. Thanks. 0 libSystem.B.dylib 0x00007fff8825e606 __kill + 10 1 libSystem.B.dylib 0x00007fff882e1c92 abort + 83 2 imap 0x0000000100069e1b default_fatal_finish + 70 3

dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap