HI, I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. I'm trying to create a very simple 2 nodes cluster to be used with NFS-ganesha. I've created the bricks and the volume. Here's the output: # gluster volume info Volume Name: cluster-demo Type: Replicate Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: glnode1:/data/brick1/gv0 Brick2: glnode2:/data/brick1/gv0 Options Reconfigured: nfs.disable: on transport.address-family: inet cluster.enable-shared-storage: enable Volume Name: gluster_shared_storage Type: Replicate Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: glnode2:/var/lib/glusterd/ss_brick Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick Options Reconfigured: transport.address-family: inet nfs.disable: on cluster.enable-shared-storage: enable However, when I'm trying to run gluster nfs-ganesha enable - it creates a wrong symbolic link and failes: # gluster nfs-ganesha enable Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue? (y/n) y This will take a few minutes to complete. Please wait .. nfs-ganesha: failed: creation of symlink ganesha.conf in /etc/ganesha failed wrong link: ganesha.conf -> /var/run/gluster/shared_storage/nfs-ganesha/ganesha.conf # ls -l /var/run/gluster/shared_storage/ total 0 I've seen some reports (and fixed) in Red Hat's Bugzilla and looked at the Red Hat solutions (https://access.redhat.com/solutions/3099581) but this doesn't help. Suggestions? I tried to upgrade to Gluster 3.12 and it seems Ganesha support was kicked out? whats replacing it? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171202/4705fb10/attachment.html>
On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote:> HI, > > I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. > > I'm trying to create a very simple 2 nodes cluster to be used with > NFS-ganesha. I've created the bricks and the volume. Here's the output: > > # gluster volume info > > Volume Name: cluster-demo > Type: Replicate > Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: glnode1:/data/brick1/gv0 > Brick2: glnode2:/data/brick1/gv0 > Options Reconfigured: > nfs.disable: on > transport.address-family: inet > cluster.enable-shared-storage: enable > > Volume Name: gluster_shared_storage > Type: Replicate > Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: glnode2:/var/lib/glusterd/ss_brick > Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick > Options Reconfigured: > transport.address-family: inet > nfs.disable: on > cluster.enable-shared-storage: enable > > However, when I'm trying to run?gluster nfs-ganesha enable - it > creates a wrong symbolic link and failes: > > # gluster nfs-ganesha enable > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the > trusted pool. Do you still want to continue? > ?(y/n) y > This will take a few minutes to complete. Please wait .. > nfs-ganesha: failed: creation of symlink ganesha.conf in /etc/ganesha > failed > > wrong link: ganesha.conf -> > /var/run/gluster/shared_storage/nfs-ganesha/ganesha.conf > > # ls -l /var/run/gluster/shared_storage/ > total 0 > > I've seen some reports (and fixed) in Red Hat's Bugzilla and looked at > the Red Hat solutions (https://access.redhat.com/solutions/3099581) > but this doesn't help. > > Suggestions?Hi, It seems you have not created directory nfs-ganesha under shared storage and plus copy/create ganesha.conf/ganesha-ha.conf inside Please follow this document http://docs.gluster.org/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/ Regards, Jiffin> > I tried to upgrade to Gluster 3.12 and it seems Ganesha support was > kicked out? whats replacing it? > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171204/45ffae27/attachment.html>
Hi Jiffin, I looked at the document, and there are 2 things: 1. In Gluster 3.8 it seems you don't need to do that at all, it creates this automatically, so why not in 3.10? 2. The step by step guide, in the last item, doesn't say where exactly do I need to create the nfs-ganesha directory. The copy/paste seems irrelevant as enabling nfs-ganesha creates automatically the ganesha.conf and a subdirectory (called "exports") with the volume share configuration file. Also, could someone tell me whats up with no ganesha on 3.12? Thanks On Mon, Dec 4, 2017 at 11:47 AM, Jiffin Tony Thottan <jthottan at redhat.com> wrote:> > > On Saturday 02 December 2017 07:00 PM, Hetz Ben Hamo wrote: > > HI, > > I'm using CentOS 7.4 with Gluster 3.10.7 and Ganesha NFS 2.4.5. > > I'm trying to create a very simple 2 nodes cluster to be used with > NFS-ganesha. I've created the bricks and the volume. Here's the output: > > # gluster volume info > > Volume Name: cluster-demo > Type: Replicate > Volume ID: 9c835a8e-c0ec-494c-a73b-cca9d77871c5 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: glnode1:/data/brick1/gv0 > Brick2: glnode2:/data/brick1/gv0 > Options Reconfigured: > nfs.disable: on > transport.address-family: inet > cluster.enable-shared-storage: enable > > Volume Name: gluster_shared_storage > Type: Replicate > Volume ID: caf36f36-0364-4ab9-a158-f0d1205898c4 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp > Bricks: > Brick1: glnode2:/var/lib/glusterd/ss_brick > Brick2: 192.168.0.95:/var/lib/glusterd/ss_brick > Options Reconfigured: > transport.address-family: inet > nfs.disable: on > cluster.enable-shared-storage: enable > > However, when I'm trying to run gluster nfs-ganesha enable - it creates a > wrong symbolic link and failes: > > # gluster nfs-ganesha enable > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the > trusted pool. Do you still want to continue? > (y/n) y > This will take a few minutes to complete. Please wait .. > nfs-ganesha: failed: creation of symlink ganesha.conf in /etc/ganesha > failed > > wrong link: ganesha.conf -> /var/run/gluster/shared_ > storage/nfs-ganesha/ganesha.conf > > # ls -l /var/run/gluster/shared_storage/ > total 0 > > I've seen some reports (and fixed) in Red Hat's Bugzilla and looked at the > Red Hat solutions (https://access.redhat.com/solutions/3099581) but this > doesn't help. > > > Suggestions? > > Hi, > > It seems you have not created directory nfs-ganesha under shared storage > and plus copy/create ganesha.conf/ganesha-ha.conf inside > Please follow this document http://docs.gluster.org/en/ > latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/ > > Regards, > Jiffin > > > > > > I tried to upgrade to Gluster 3.12 and it seems Ganesha support was kicked > out? whats replacing it? > > > > _______________________________________________ > Gluster-users mailing listGluster-users at gluster.orghttp://lists.gluster.org/mailman/listinfo/gluster-users > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171204/056ede28/attachment.html>