On Tue, Jun 21, 2011 at 2:37 PM, Adrian Carpenter <span dir="ltr"><<a href="mailto:tac12@wbic.cam.ac.uk">tac12@wbic.cam.ac.uk</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm evaluating geo-replication feature of 3.2.1, and today two of the volumes that I am replicating have both stopped with the same error )although different files, here are some logs:<br>
<br>
File "/opt/glusterfs/3.2.1/local/libexec/glusterfs/python/syncdaemon/master.py", line 215, in crawl<br>
raise RuntimeError("timestamp corruption for " + path)<br>
RuntimeError: timestamp corruption for ./x86_64/freesurfer4/freesurfer-4.0.5/mni/include/bicpl<br>
<br>
I have deleted the file and copied it back from another source, which appears to fix the problem, although of course in a test environment this is OK, in production it would be an issue.<br>
<br>
Are there other suggestions to correct this problem?<br>
<br>
Adrian<br>
<br>
p.s. the volume is replicated.<br><br></blockquote><div><br></div><div>Adrian, </div><div>Thanks for reporting this bug. We will look in to this issue. This exception should be trapped and healed appropriately. Will file a bug and keep you in the loop.</div>
</div><div> </div><div>Csaba, can you please followup.</div><div><br></div><div>-- <br>Anand Babu Periasamy<br>Blog [<a href="http://www.unlocksmith.org/" target="_blank">http://www.unlocksmith.org</a>]<br><br>Imagination is more important than knowledge --Albert Einstein<br>
</div>