I tried to fix a different problem by going from 3.4.4 to 3.6.0 in 
fedora-updates-testing, but when I restarted the server I saw a bunch of:

Jun 10 20:54:39 mail cyrus/ctl_cyrusdb[20672]: mbentry has no uniqueid, needs 
reconstruct: mboxname=<I3fe40d49490fd247> syserror=<No such file or directory> 
func=<mailbox_open_advanced>
Jun 10 20:54:39 mail cyrus/ctl_cyrusdb[20672]: IOERROR: opening index failed: 
mailbox=<I3fe40d49490fd247> error=<System I/O error> syserror=<No such file or 
directory> func=<mailbox_open_advanced>

and I tried running chk_cyrus to resolve the problem, but got:

...
checking: I5e8440be4aeb406b
checking: I5eb3597f431e388c
bad mailbox I5ef2c91d-0ae5-40e3-a046-1546141cdf69 in chkmbox
fatal error: fatal error


I googled this and didn't see much, but someone pointed out that chk_cyrus 
hasn't been touched in a while and might not even be working reliably.

Reading www.cyrusimap.org/imap/reference/faqs/o-reconstruct.html indicated that 
reconstruct -m doesn't work, but I don't think that's my problem.

I also tried:

reconstruct -r -f user.existent
reconstruct -r -f user.nonexistent
reconstruct -r -f user/existent
reconstruct -r -f user/nonexistent

and they all succeed (exit 0) with no output.  chk_cyrus -M user.nosuch also 
fails to generate any output or non-zero exit status.

I followed the directions in 
www.cyrusimap.org/imap/reference/admin/sop/reconstructing.html but that didn't 
make any apparent difference.

Is there a guide to identifying and fixing mailbox damage?

Thanks

------------------------------------------
Cyrus: Info
Permalink: 
https://cyrus.topicbox.com/groups/info/Td92cdcb1147fe6d1-M48df05501f16edc3db190f66
Delivery options: https://cyrus.topicbox.com/groups/info/subscription

Reply via email to