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

Logan Barfield lbarfield at tqhosting.com
Fri Oct 23 15:01:56 UTC 2015


We're currently running Gluster 3.6.5 on CentOS 6.  We are planning on
upgrading to 3.7.x sometime soon if that will resolve our issues, but this
being a high traffic production environment it's hard to schedule downtime
to do so.

We have also tried creating a new, empty slave volume, and setting up a new
geo-replication link.  Even with that all of the data on the master isn't
copied.  It get's about half-way, goes into "Changelog Crawl" mode, and
then only syncs new data.  Because of that we've stopped using
geo-replication for now, and set up some rsync scripts instead.

If there's a 100% effective and officially supported way of forcing a full
sync that would be great.  None of the suggestions/tips/workarounds I've
seen on the lists so far have worked to do so.




Thank You,

Logan Barfield
Tranquil Hosting

On Fri, Oct 23, 2015 at 1:26 AM, Aravinda <avishwan at redhat.com> wrote:

> 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 listGluster-users at gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151023/c6638451/attachment.html>


More information about the Gluster-users mailing list