On Tue, Jun 21, 2011 at 2:37 PM, Adrian Carpenter <tac12 at wbic.cam.ac.uk>wrote:
> 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:
>
> File
> "/opt/glusterfs/3.2.1/local/libexec/glusterfs/python/syncdaemon/master.py",
> line 215, in crawl
> raise RuntimeError("timestamp corruption for " + path)
> RuntimeError: timestamp corruption for
> ./x86_64/freesurfer4/freesurfer-4.0.5/mni/include/bicpl
>
> 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.
>
> Are there other suggestions to correct this problem?
>
> Adrian
>
> p.s. the volume is replicated.
>
>
Adrian,
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.
Csaba, can you please followup.
--
Anand Babu Periasamy
Blog [http://www.unlocksmith.org]
Imagination is more important than knowledge --Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gluster.org/pipermail/gluster-users/attachments/20110627/cc42af7a/attachment.htm>
