Hi Kaushal,
I’m using
->gluster --version glusterfs 3.5.2 built on Aug 6 2014 19:33:49 GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
and the generated brick.vol has this line(s)
volume dnas_volume-locks type features/locks subvolumes dnas_volume-access-control end-volume
and you are right. No these aren’t NFS mounted, that was poorly worded. Should I just update glusterfs that should resolve my problems? Or am I still missing something.
Thanks, Jordan
Which version of GlusterFS are you using? The locks translator should be enabled by default for all volumes for the latest versions (IIRC 3.5 and above). So you wouldn't need to do anything. To verify you can check the generated brick volfiles in /var/lib/glusterd/vols/<VOL>/<brick-name>.vol . Also, are you really creating GlusterFS bricks on NFS mounts? That doesn't work.. ~kaushal On Sat, Jul 4, 2015 at 7:16 AM, Jordan Willis < jwillis0720@xxxxxxxxx> wrote: Hi,
Is it possible to enable posix type locking with glusterfs without shutting off the volume?
I think this is what I need (I’m trying to get sqlite to lock files on my nfs mounted glusterfs volume)
volume locks type features/locks subvolumes brick end-volume
Can you enable this with the gluster volume set command in some way? If not, do I just add those lines to the /etc/glusterfs/gluster.vol file and turn off and on the volume, or how would I reload that file. I manually started the current fs with the following. I’m confused on where I should actually enable the locking.
gluster volume create myvolume nfs_mount_1 nfs_mount_2 …nfs_mount_N gluster volume start myvolume
Thanks so much, Jordan
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users