[Gluster-users] Geo-Replication "FILES SKIPPED"

[Aravinda]

Hi,

First error "Operation not permitted" looks like due to GFID conflict. 
We are working on auto resolving GFID conflict issues so that 
Geo-replication will not halt due to these issues. Please let us know 
which version of Gluster you are using so that we can provide workaround 
steps to re-sync the Skipped files.

Log file records Skipped files GFIDs, we can retrigger the sync for 
those GFIDs if required. Sometimes these errors(rsync/tar) are due to 
errors in some files but Geo-replication records as SKIPPED for the 
entire batch. We are working on recording failures more granular.

regards
Aravinda

On 10/14/2015 08:36 PM, Logan Barfield wrote:
> We had a connectivity issue on a "tar+ssh" geo-rep link yesterday that
> caused a lot of issues.  When the link came back up it immediately went
> into a "faulty" state, and the logs were showing "Operation not permitted"
> and "File Exists" errors in a loop.
>
> We were finally able to get things back on track by shutting down the
> geo-rep link, killing the hung tar processes on the slave, and bringing the
> link back up in "rsync" mode.
>
> The master is now back in a "Changelog Crawl" status, and I have confirmed
> new files are being copied to the slave correctly.
>
> The status on the master is currently showing 100k+ "FILED SKIPPED."
>
> My question is: Where can I see which files were skipped, and how can I
> force them to replicate/update to the slave?
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151023/91db637e/attachment.html>