<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 16, 2019 at 11:36 PM Strahil <<a href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">By the way,<br>
<br>I have been left with the impresssion that data is transferred via 'rsync' and not via FUSE.<br>Am I wrong ?<br></blockquote><div><br></div><div>Rsync syncs data from Master FUSE mount to Slave/Remote FUSE mount.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>Best Regards,<br>Strahil NikolovOn Oct 16, 2019 19:59, Alexander Iliev <<a href="mailto:ailiev%2Bgluster@mamul.org" target="_blank">ailiev+gluster@mamul.org</a>> wrote:<br>><br>> Hi Aravinda,<br>><br>> All volume brick on the slave volume are up and the volume seems functional.<br>><br>> Your suggestion about trying to mount the slave volume on a master node <br>> brings up my question about network connectivity again - the GlusterFS <br>> documentation[1] says:<br>><br>> > The server specified in the mount command is only used to fetch the <br>> gluster configuration volfile describing the volume name. Subsequently, <br>> the client will communicate directly with the servers mentioned in the <br>> volfile (which might not even include the one used for mount).<br>><br>> To me this means that the masternode from your example is expected to <br>> have connectivity to the network where the slave volume runs, i.e. to <br>> have network access to the slave nodes. In my geo-replication scenario <br>> this is definitely not the case. The two cluster are running in two <br>> completely different networks that are not interconnected.<br>><br>> So my question is - how is the slave volume mount expected to happen if <br>> the client host cannot access the GlusterFS nodes? Or is the <br>> connectivity a requirement even for geo-replication?<br>><br>> I'm not sure if I'm missing something, but any help will be highly <br>> appreciated!<br>><br>> Thanks!<br>><br>> Links:<br>> [1] <br>> <a href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Setting%20Up%20Clients/" rel="noreferrer" target="_blank">https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Setting%20Up%20Clients/</a><br>> --<br>> alexander iliev<br>><br>> On 10/16/19 6:03 AM, Aravinda Vishwanathapura Krishna Murthy wrote:<br>> > Hi Alexander,<br>> > <br>> > Please check the status of Volume. Looks like the Slave volume mount is <br>> > failing because bricks are down or not reachable. If Volume status shows <br>> > all bricks are up then try mounting the slave volume using mount command.<br>> > <br>> > ```<br>> > masternode$ mkdir /mnt/vol<br>> > masternode$ mount -t glusterfs <slavehost>:<slavevol> /mnt/vol<br>> > ```<br>> > <br>> > On Fri, Oct 11, 2019 at 4:03 AM Alexander Iliev <br>> > <<a href="mailto:ailiev%2Bgluster@mamul.org" target="_blank">ailiev+gluster@mamul.org</a> <mailto:<a href="mailto:ailiev%252Bgluster@mamul.org" target="_blank">ailiev%2Bgluster@mamul.org</a>>> wrote:<br>> > <br>> > Hi all,<br>> > <br>> > I ended up reinstalling the nodes with CentOS 7.5 and GlusterFS 6.5<br>> > (installed from the SIG.)<br>> > <br>> > Now when I try to create a replication session I get the following:<br>> > <br>> > > # gluster volume geo-replication store1 <slave-host>::store2 create<br>> > push-pem<br>> > > Unable to mount and fetch slave volume details. Please check the<br>> > log:<br>> > /var/log/glusterfs/geo-replication/gverify-slavemnt.log<br>> > > geo-replication command failed<br>> > <br>> > You can find the contents of gverify-slavemnt.log below, but the<br>> > initial<br>> > error seems to be:<br>> > <br>> > > [2019-10-10 22:07:51.578519] E<br>> > [fuse-bridge.c:5211:fuse_first_lookup]<br>> > 0-fuse: first lookup on root failed (Transport endpoint is not<br>> > connected)<br>> > <br>> > I only found<br>> > [this](<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1659824" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1659824</a>)<br>> > bug report which doesn't seem to help. The reported issue is failure to<br>> > mount a volume on a GlusterFS client, but in my case I need<br>> > geo-replication which implies the client (geo-replication master) being<br>> > on a different network.<br>> > <br>> > Any help will be appreciated.<br>> > <br>> > Thanks!<br>> > <br>> > gverify-slavemnt.log:<br>> > <br>> > > [2019-10-10 22:07:40.571256] I [MSGID: 100030]<br>> > [glusterfsd.c:2847:main] 0-glusterfs: Started running glusterfs version<br>> > 6.5 (args: glusterfs --xlator-option=*dht.lookup-unhashed=off<br>> > --volfile-server <slave-host> --volfile-id store2 -l<br>> > /var/log/glusterfs/geo-replication/gverify-slavemnt.log<br>> > /tmp/gverify.sh.5nFlRh)<br>> > > [2019-10-10 22:07:40.575438] I [glusterfsd.c:2556:daemonize]<br>> > 0-glusterfs: Pid of current running process is 6021<br>> > > [2019-10-10 22:07:40.584282] I [MSGID: 101190]<br>> > [event-epoll.c:680:event_dispatch_epoll_worker] 0-epoll: Started thread<br>> > with index 0<br>> > > [2019-10-10 22:07:40.584299] I [MSGID: 101190]<br>> ></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>regards<br></div>Aravinda VK<br></div></div></div></div></div></div></div>