Since some people might want to enforce quota on the server (enforcing on the client makes the system trivially susceptible to cheating), I tried running the quota translator there.  The result was segfaults in quota_lookup_cbk.  Looking deeper, it turns out that the cutting and pasting from quota to marker has resulted in several symbols with duplicate names:

      2 fini
      2 _fini
      2 init
      2 _init
      2 mem_acct_init
      2 quota_forget*
      2 quota_inode_loc_fill*
      2 quota_local_new*
      2 quota_loc_fill*
      2 reconfigure

Several of these are looked up using dlsym and accessed via the returned pointers, so they function properly despite the duplication.  The ones marked with asterisks are more problematic.  Because of the way we do dynamic loading, marker is loaded first and then quota resolves against the marker versions of the duplicate symbols.  Since e.g. marker's version of quota_local_new is doing completely different initialization on a completely different structure than what callers in quota expect, it should be unsurprising that subsequent use of the returned pointer from within quota results in a segfault.  The only surprise is that we get as far as quota_lookup_cbk before the crash.

*** Bug 2688 has been marked as a duplicate of this bug. ***

CHANGE: http://review.gluster.com/381 (This is to fix to bug marker translator and quota translator cannot co-exist in same process.) merged in master by Vijay Bellur (vijay)

copied the quota information from client vol-file to the server vol-file.

and still able to do the filesystem operations on the mount point

glusterfs#10.1.12.134:one-br on /mnt/glfs type fuse (rw,allow_other,default_permissions,max_read=131072)
[root@Centos1 ~]# cd /mnt/glfs
[root@Centos1 glfs]# ls
a  dir  dir3  kill
[root@Centos1 glfs]# touch abc
[root@Centos1 glfs]# mkdir dir/dir-n
[root@Centos1 glfs]#