<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:706153.78297.qm@web30501.mail.mud.yahoo.com"
type="cite">
<blockquote type="cite">
<pre wrap="">
Sounds like bad RAM maybe corrupting the cyrus
databases... Any other
indication of file corruption or system
locking/freezing/rebooting
(things associated with bad memory) ?
In a PC I'd run memtest86, dunno if that option is
available to you.
-Blake
----
Cyrus Home Page: <a class="moz-txt-link-freetext" href="http://cyrusimap.web.cmu.edu/">http://cyrusimap.web.cmu.edu/</a>
Cyrus Wiki/FAQ: <a class="moz-txt-link-freetext" href="http://cyrusimap.web.cmu.edu/twiki">http://cyrusimap.web.cmu.edu/twiki</a>
List Archives/Info:
<a class="moz-txt-link-freetext" href="http://asg.web.cmu.edu/cyrus/mailing-list.html">http://asg.web.cmu.edu/cyrus/mailing-list.html</a>
</pre>
</blockquote>
<pre wrap=""><!---->
No signs of bad memory, the server operates off a
fiber channel RAID and there are no warnings or
failures with that either. There are a couple of
utilities i can try to test the memory, but i will not
have an answer on that until this weekend.
Why would reconstruct -i work (minus the few
disappearing emails) and reconstruct -r user/short
name corrupt the inbox? I have to assume if the inbox
didn't get corrupted that the missing emails in
question would be there. I have tried to copy emails
from inbox to a folder in side the usernames folder,
upon a reconstruct -r those emails are now viewable,
but the main inbox is still corrupt.
Just a few things I tried if any of this helps.
Thanks again for you help in advance
Derrick
</pre>
</blockquote>
I'm honestly not familiar with the "-i" option as my 2.3 systems do not
seem to have that option and I seem to only run reconstruct when
restoring backups so I don't use it very often on individual mailboxes.
The fact that files seem to disappear no mater what, and the problem is
reproducible, seems to indicate there is some larger problem. I haven't
heard of this being a wide-spread problem I'm going to assume this is
something with your config or scenario not common to all Cyrus
installations. <br>
<br>
One of the tests I've used to burn in new systems and test for file
corruption is to take a large file (an iso or dd if=/dev/urandom works
fine) and compute the md5sum. Then copy the file and compute the md5sum
on the copy. Compare, delete, and repeat via shell script. This could
be from one drive to another, one partition to another, or just one
file to a different file.<br>
<br>
Might try something similar to test your system, and it doesn't even
require a maintenance window...<br>
</body>
</html>