File: o-reconstruct.rst.txt

package info (click to toggle)
cyrus-imapd 3.10.0~beta1-3
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 86,332 kB
  • sloc: ansic: 284,810; perl: 135,824; javascript: 9,562; sh: 5,728; yacc: 2,565; cpp: 2,147; makefile: 2,133; lex: 662; xml: 621; awk: 303; python: 279; asm: 262
file content (30 lines) | stat: -rw-r--r-- 1,311 bytes parent folder | download | duplicates (20)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Why does reconstruct -m not work?
---------------------------------

From the :cyrusman:`reconstruct(8)` man page::

    −m     NOTE: CURRENTLY UNAVAILABLE
                 Rebuild  the  mailboxes file.  Use whatever data in the existing
                 mailboxes file it can scavenge, then scans all partitions listed
                 in the imapd.conf(5) file for additional mailboxes.
                 
Reconstruct is currently unable to rebuild the mailboxes db, and 
comments on the mailing list indicate this ability will not be added; at 
least, not any time soon. 

The solution here is to make sure that you back up your mailboxes db, 
preferably including a plain-text copy of it. Please see Backups for 
more information. 

If you do find yourself with a corrupted mailboxes.db, there are a few 
things you can try. The first is to see if ``db_recover`` can recover 
your database. If that doesnt' work, there should be backups in 
``$CONFIGDIRECTORY/db.backup1`` and ``$CONFIGDIRECTORY/db.backup2`` that 
may be OK. 

If you're using Simon Matter's RPMs, plain-text copies of the mailboxes 
database should be being generated and saved in 
``/var/lib/imap/backup``. Try rebuilding the db from one of those using 
:cyrusman:`ctl_mboxlist(8)`. Alternately, try asking the mailing list 
for help.