<html><body><p>All... I need your help! I am trying to setup Highly available Active-Active Ganesha configuration on two glusterfs nodes based on instructions here: <br><br><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> and <br><a href="http://www.slideshare.net/SoumyaKoduri/high-49117846">http://www.slideshare.net/SoumyaKoduri/high-49117846</a> and <br><a href="https://www.youtube.com/watch?v=Z4mvTQC-efM">https://www.youtube.com/watch?v=Z4mvTQC-efM</a>.<br><br><br><b>My questions:</b><br><br>1. what is the expected behvaior? Is the cluster.enable-shared-storage command expected to create shared storage? It seems odd to return a success message without creating the shared volume.<br>2. Any suggestions on how to get past this problem? <br><br><b>Details:</b><br>I am using glusterfs 3.7.5 and Ganesha 2.2.0.6 installable packages. I'm 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 /run/gluster/ and automounts the shared volume for HA.<br><br>This command was working perfectly fine, and I was able to setup ganesha 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 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 different cloud. and when I run the same command there, (same version of glusterfs and ganesha, same cent OS 7) - the command returned successfully, but it did not auto create the shared_storage directory. There were no logs either in /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 on /var/run/gluster/9d5e1ba5e44bd1aa3331d2ee752a806a.socket failed (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 /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 command expected to create shared storage? It seems odd to return a success message without creating the shared volume.<br>2. Any suggestions on how to get past this problem?<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>
</body></html>