<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Dear Bron<br>
<br>
After running reconstruct - r -f -G on both client and replica and
after about 22 hours all seems OK with no indications of any syncing
errors.<br>
<br>
There were some errors on some mailboxes while the reconstruct was run
but none since.<br>
<br>
Thanks<br>
Stephen Carr<br>
<br>
Bron Gondwana wrote:
<blockquote cite="mid:20101205012810.GA6422@brong.net" type="cite">
<pre wrap="">On Sun, Dec 05, 2010 at 10:27:27AM +1030, Stephen Carr wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear All
My prior idea was incorrect
I just got this see below
There was nothing reported by fuser in the users INBOX.
So I ran reconstrust -f -r -G on both client and replica as per
Bron's idea.
Did a sync_client -v -l -m user.USER was OK
The started a rolling sync_client - seems OK
Should I ro a reconstruct on all users?
</pre>
</blockquote>
<pre wrap=""><!---->
It's fine to run a reconstruct on all users. -G will upgrade
all you cache records as well, but it costs the most in IO!
-s is the cheapest, and will find missing files or corrupt
indexes still.
Bron.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Stephen Carr
School of Civil, Environmental & Mining Engineering
The University of Adelaide
Adelaide, South Australia, 5005
Australia
Tel +618-8303-4313
Fax +618-8303-4359
Email <a class="moz-txt-link-abbreviated" href="mailto:sgcarr@civeng.adelaide.edu.au">sgcarr@civeng.adelaide.edu.au</a>
CRICOS Provider Number 00123M
-----------------------------------------------------------
This email message is intended only for the addressee(s) and
contains information that may be confidential and/or copyright.
If you are not the intended recipient please notify the sender
by reply email and immediately delete this email. Use, disclosure
or reproduction of this email by anyone other than the intended
recipient(s) is strictly prohibited. No representation is made
that this email or any attachments are free of viruses. Virus
scanning is recommended and is the responsibility of the recipient.
</pre>
</body>
</html>