[Gluster-users] new warning with geo-rep: _GMaster: ENTRY FAILED:

[ML mail]

Thanks for the info. Somehow geo-rep doesn't work well for me, each time I try to fix something with the help of the mailing list there is another issue or problem. So I will simply delete the whole geo-rep, upgrade to 3.7.9 as soon as available, and re-create the geo-rep session. Hopefully this will help.

Regards
ML




On Wednesday, March 2, 2016 6:51 AM, Aravinda <avishwan at redhat.com> wrote:
Hi ML,

While creating file "fileKey", ENOENT error is seen. Since Entry 
"fileKey" is not created, rsync failed with "Operation not permitted" error.

ENOENT during create happens only when parent directory does not exists 
on Slave or exists with different GFID.

regards
Aravinda


On 03/01/2016 11:08 PM, ML mail wrote:
> Hi,
>
> I recently updated GlusterFS from 3.7.6 to 3.7.8 on my two nodes master volume (one brick per node) and slave node. Today I noticed a new type of warning which I never saw before.
>
> On the master node's geo-replication log file I see quite a few of these:
>
>
> [2016-03-01 16:28:08.446464] W [master(/data/myvolume/brick):822:log_failures] _GMaster: ENTRY FAILED: ({'uid': 33, 'gfid': 'f1d6271b-b0eb-4f4b-91c6-02f4a967954a', 'gid': 33, 'mode': 33188, 'entry': '.gfid/51128ceb-84c4-41f1-9d5c-dac238258946/fileKey', 'op': 'CREATE'}, 2)
>
>
> And then on the slave node geo-replication-slave log file I see a few of these:
>
>
> [2016-03-01 16:28:16.954456] W [fuse-bridge.c:1991:fuse_create_cbk] 0-glusterfs-fuse: 11856: /.gfid/f1d6271b-b0eb-4f4b-91c6-02f4a967954a => -1 (Operation not permitted)
>
> The FAILED counter on the geo-rep status tool also increased respectively.
>
> Any ideas what could be going wrong? or is this also some bug which will be fixed in 3.7.9?
>
> Regards
> ML
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users