search for: mail_index_mark_corrupted

Displaying 2 results from an estimated 2 matches for "mail_index_mark_corrupted".

2006 Oct 13
1
Segfault in in rc7 when index does not exists
...EGV, Segmentation fault. mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at mail-index.c:1313 1313 memcpy(index->map->mmap_base, hdr, hdr_size); (gdb) bt #0 mail_index_write_base_header (index=0x80e2a28, hdr=0xaff66028) at mail-index.c:1313 #1 0x080902eb in mail_index_mark_corrupted (index=0x80e2a28) at mail-index.c:1839 #2 0x0809ca30 in mail_transaction_log_file_create (log=0x80e3928, path=0x80d2130 "/dovecot.index.log", dev=0, ino=0, file_size=0) at mail-transaction-log.c:575 #3 0x0809e138 in mail_transaction_log_file_open_or_create (log=0x80e3928, path=0x80d2130...
2005 Jul 20
1
Corrupted indices (and accidental checkin)
I've seen a number of corrupted-index problems pop up on our test-dovecot servers (used by a few people at the office), and I'm wondering why corrupt indices don't just automatically get deleted ? Something like: if (!MAIL_INDEX_IS_IN_MEMORY(index)) { unlink(index->filepath); } in src/lib-index/mail-index.c:mail_index_set_error() comes to mind. It