On 11/17/2015 10:21 PM, Surya K Ghatty wrote:
Hi:
I am trying to understand if it is technically feasible to have gluster
nodes on one machine, and export a volume from one of these nodes using
a nfs-ganesha server installed on a totally different machine? I tried
the below and showmount -e does not show my volume exported. Any
suggestions will be appreciated.
1. Here is my configuration:
Gluster nodes: glusterA and glusterB on individual bare metals - both in
Trusted pool, with volume gvol0 up and running.
Ganesha node: on bare metal ganeshaA.
2. my ganesha.conf looks like this with IP address of glusterA in the FSAL.
FSAL {
Name = GLUSTER;
# IP of one of the nodes in the trusted pool
*hostname = "WW.ZZ.XX.YY" --> IP address of GlusterA.*
# Volume name. Eg: "test_volume"
volume = "gvol0";
}
3. I disabled nfs on gvol0. As you can see, *nfs.disable is set to on.*
[root@glusterA ~]# gluster vol info
Volume Name: gvol0
Type: Distribute
Volume ID: 16015bcc-1d17-4ef1-bb8b-01b7fdf6efa0
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: glusterA:/data/brick0/gvol0
Options Reconfigured:
*nfs.disable: on*
nfs.export-volumes: off
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
performance.readdir-ahead: on
4. I then ran ganesha.nfsd -f /etc/ganesha/ganesha.conf -L
/var/log/ganesha.log -N NIV_FULL_DEBUG
Ganesha server was put in grace, no errors.
17/11/2015 10:44:40 : epoch 564b5964 : ganeshaA:
nfs-ganesha-26426[reaper] fridgethr_freeze :RW LOCK :F_DBG :Released
mutex 0x7f21a92818d0 (&fr->mtx) at
/builddir/build/BUILD/nfs-ganesha-2.2.0/src/support/fridgethr.c:484
17/11/2015 10:44:40 : epoch 564b5964 : ganeshaA:
nfs-ganesha-26426[reaper] nfs_in_grace :RW LOCK :F_DBG :Acquired mutex
0x7f21ad1f18e0 (&grace.g_mutex) at
/builddir/build/BUILD/nfs-ganesha-2.2.0/src/SAL/nfs4_recovery.c:129
*17/11/2015 10:44:40 : epoch 564b5964 : ganeshaA :
nfs-ganesha-26426[reaper] nfs_in_grace :STATE :DEBUG :NFS Server IN GRACE*
17/11/2015 10:44:40 : epoch 564b5964 : ganeshaA :
nfs-ganesha-26426[reaper] nfs_in_grace :RW LOCK :F_DBG :Released mutex
0x7f21ad1f18e0 (&grace.g_mutex) at
/builddir/build/BUILD/nfs-ganesha-2.2.0/src/SAL/nfs4_recovery.c:141
You shall still need gluster-client bits on the machine where
nfs-ganesha server is installed to export a gluster volume. Check if you
have got libgfapi.so installed on that machine.
Also, ganesha server does log the warnings if its unable to process the
EXPORT/FSAL block. Please recheck the logs if you have got any.
Thanks,
Soumya
5. [root@ganeshaA glusterfs]# showmount -e
Export list for ganeshaA:
<empty>
Any suggestions on what I am missing?
Regards,
Surya Ghatty
"This too shall pass"
________________________________________________________________________________________________________
Surya Ghatty | Software Engineer | IBM Cloud Infrastructure Services
Development | tel: (507) 316-0559 | [email protected]
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
