Hi, As a quick workaround for geo-replication to work. Please configure the following option.
gluster vol geo-replication <mastervol> <slavehost>::<slavevol> config access_mount true The above option will not do the lazy umount and as a result, all the master and slave volume mounts maintained by geo-replication can be accessed by others. It's also visible in df output. There might be cases where the mount points not get cleaned up when worker goes faulty and come back. These needs manual cleaning. Thanks, Kotresh HR On Tue, Feb 6, 2018 at 12:37 AM, Florian Weimer <fwei...@redhat.com> wrote: > On 02/05/2018 01:33 PM, Florian Weimer wrote: > > Do you have strace output going further back, at least to the proceeding >> getcwd call? It would be interesting to see which path the kernel reports, >> and if it starts with "(unreachable)". >> > > I got the strace output now, but it very difficult to read (chdir in a > multi-threaded process …). > > My current inclination is to blame rsync because it does an unconditional > getcwd during startup, which now fails if the current directory is > unreachable. > > Further references: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00152.html > https://bugzilla.redhat.com/show_bug.cgi?id=1542180 > > Andreas Schwab agrees that rsync is buggy: > > https://sourceware.org/ml/libc-alpha/2018-02/msg00153.html > > > Thanks, > Florian > _______________________________________________ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users > -- Thanks and Regards, Kotresh H R
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
