<html><body><p>Hi Soumya, Avra,<br><br>The gluster_shared_storage volume has not be created, and there is no shared_storage directory that has been created. The gluster peer status shows the two nodes (gluster1, and gluster2) are up and running. Also, restarting the glusterd on either machines did not make any difference. <br><br>I used to have a three node setup (gluster3, in addition to the above setup), and I detached one of them uninstalled gluster on it. <font size="4">jiffin </font>and <font size="4">kkeithley_ </font>pointed on ganesha irc channel, "<font size="2" color="#333333" face="Arial">I think it didn't work because it wants three nodes/bricks to make a "replica 3" volume</font>"<br><br>I cleaned up glusterd on the remaining machines by stopping the glusterd, deleting /var/run/gluster/* and then restarted glusterd on both machines. It is at this point that the cluster.enable-shared-storage seemed to work.<br><br><tt>>Has the "gluster_shared_storage" volume creation itself failed? Verify <br>>in 'gluster volume info'.<br>>Also check if the gluster nodes are in healthy state 'gluster peer <br>>status'. Try restarting 'glusterd' service on both the nodes.</tt><br><br>My observation:<br>1. I would expect the script to return unsuccessful if the creation of gluster_shared_volume or shared directory fails. The command currently returns successful message.<br>2. The command should display an appropriate error message indicating what went wrong. Instead, there is no indication either in the logs or on the console that something failed.<br><br>Let me know what you think.<br><br>Regards,<br><br>Surya Ghatty<br><br>"This too shall pass"<br>________________________________________________________________________________________________________<br>Surya Ghatty | Software Engineer | IBM Cloud Infrastructure Services Development | tel: (507) 316-0559 | ghatty@us.ibm.com<br><br><br><img width="16" height="16" src="cid:1__=8FBBF46BDFF4374A8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Soumya Koduri ---11/06/2015 11:18:39 AM---On 11/05/2015 08:43 PM, Surya K Ghatty wrote: > All... I ne"><font color="#424282">Soumya Koduri ---11/06/2015 11:18:39 AM---On 11/05/2015 08:43 PM, Surya K Ghatty wrote: > All... I need your help! I am trying to setup Highly</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Soumya Koduri <skoduri@redhat.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Surya K Ghatty/Rochester/IBM@IBMUS, gluster-users@gluster.org</font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">Avra Sengupta <asengupt@redhat.com></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">11/06/2015 11:18 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [Gluster-users] Question on HA Active-Active Ganesha setup</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><br><br>On 11/05/2015 08:43 PM, Surya K Ghatty wrote:<br>> All... I need your help! I am trying to setup Highly available<br>> Active-Active Ganesha configuration on two glusterfs nodes based on<br>> instructions here:<br>><br>> </tt><tt><a href="https://gluster.readthedocs.org/en/latest/Administrator%20Guide/Configuring%20HA%20NFS%20Server/">https://gluster.readthedocs.org/en/latest/Administrator%20Guide/Configuring%20HA%20NFS%20Server/</a></tt><tt><br>> and<br>> </tt><tt><a href="http://www.slideshare.net/SoumyaKoduri/high-49117846">http://www.slideshare.net/SoumyaKoduri/high-49117846</a></tt><tt> and<br>> </tt><tt><a href="https://www.youtube.com/watch?v=Z4mvTQC-efM">https://www.youtube.com/watch?v=Z4mvTQC-efM</a></tt><tt>.<br>><br>><br>> *My questions:*<br>><br>> 1. what is the expected behvaior? Is the cluster.enable-shared-storage<br>> command expected to create shared storage? It seems odd to return a<br>> success message without creating the shared volume.<br>> 2. Any suggestions on how to get past this problem?<br>><br>> *Details:*<br>> I am using glusterfs 3.7.5 and Ganesha 2.2.0.6 installable packages. I'm<br>> installing<br>><br>> Also, I am using the following command<br>><br>> gluster volume set all cluster.enable-shared-storage enable<br>><br>> that would automatically setup the shared_storage directory under<br>> /run/gluster/ and automounts the shared volume for HA.<br>><br>> This command was working perfectly fine, and I was able to setup ganesha<br>> HA successfully on cent OS 7.0 running on bare metals - until now.<br>><br>><br>><br>> [root@qint-tor01-c7 gluster]# gluster vol set all<br>> cluster.enable-shared-storage enable<br>> volume set: success<br>><br>> [root@qint-tor01-c7 gluster]# pwd<br>> /run/gluster<br>><br>> [root@qint-tor01-c7 gluster]# ls<br>> 5027ba011969a8b2eca99ca5c9fb77ae.socket shared_storage<br>> changelog-9fe3f3fdd745db918d7d5c39fbe94017.sock snaps<br>> changelog-a9bf0a82aba38610df80c75a9adc45ad.sock<br>><br>><br>> Yesterday, we tried to deploy Ganesha HA with Gluster FSAL on a<br>> different cloud. and when I run the same command there, (same version of<br>> glusterfs and ganesha, same cent OS 7) - the command returned<br>> successfully, but it did not auto create the shared_storage directory.<br>> There were no logs either in<br>> /var/log/glusterfs/etc-glusterfs-glusterd.vol.log<br>><br>> or /var/log/ganesha.log related to the command.<br>><br>> However, I do see these logs written to the etc-glusterfs-glusterd.vol.log<br>><br>> [2015-11-05 14:43:00.692762] W [socket.c:588:__socket_rwv] 0-nfs: readv<br>> on /var/run/gluster/9d5e1ba5e44bd1aa3331d2ee752a806a.socket failed<br>> (Invalid argument)<br>><br>> on both ganesha nodes independent of the commands I execute.<br>><br>> regarding this error, I did a ss -x | grep<br>> /var/run/gluster/9d5e1ba5e44bd1aa3331d2ee752a806a.socket<br>><br>> and it appears that no process was using these sockets, on either machines.<br>><br>> My questions:<br>><br>> 1. what is the expected behvaior? Is the cluster.enable-shared-storage<br>> command expected to create shared storage? It seems odd to return a<br>> success message without creating the shared volume.<br>yes. This command creates the volume "gluster_shared_storage" and <br>mounts it at '/run/gluster/shared_storage'.<br><br>> 2. Any suggestions on how to get past this problem?<br>Has the "gluster_shared_storage" volume creation itself failed? Verify <br>in 'gluster volume info'.<br>Also check if the gluster nodes are in healthy state 'gluster peer <br>status'. Try restarting 'glusterd' service on both the nodes.<br><br>CCin Avra who may provide more details.<br><br>Thanks,<br>Soumya<br><br>> Regards,<br>><br>> Surya Ghatty<br>><br>> "This too shall pass"<br>> ________________________________________________________________________________________________________<br>> Surya Ghatty | Software Engineer | IBM Cloud Infrastructure Services<br>> Development | tel: (507) 316-0559 | ghatty@us.ibm.com<br>><br>><br>><br>> _______________________________________________<br>> Gluster-users mailing list<br>> Gluster-users@gluster.org<br>> </tt><tt><a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></tt><tt><br>><br><br></tt><br><BR>
</body></html>