Description of problem:
Enabling ACL for the samba mounted filesystem automated by gluster volume start.

When a gluster volume is started, the first time it appends an entry to the /etc/fstab file with the samba mount point. This step is performed by the hook script - /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh

However this entry in the fstab file does not enable ACL option. To automate this, the hook script was edited to add 'acl' in the options. When the gluster was started the first time, it added the acl option in the fstab file as described below:
ad-rhs-srv1.cloud.lab.eng.bos.redhat.com:/dfilevol01 /mnt/samba/dfilevol01 glusterfs defaults,acl,transport=tcp 0 0

However the acl option does not take effect in the mounted filesystem /mnt/samba/dfilevol01. When the filesystem is manually unmounted and mounted again, acl gets enabled.



Version-Release number of selected component (if applicable):
RHS 2.0
2.6.32-220.34.1.el6  (Anshi Update 4)



How reproducible:


Steps to Reproduce:
1. Create a new gluster volume
2. Edit the hook - /var/lib/glusterd/hooks/1/start/post/S30samba-start.sh and add 'acl' next to defaults in the fstab section.
[mntent="`hostname`:/$volname $mntpt glusterfs defaults,acl,transport=tcp 0 0"]
3. Start the gluster volume, verify the samba mount using df -h command and check mount options by running "mount" command:

Actual results:
# mount | grep new
ad-rhs-srv1.cloud.lab.eng.bos.redhat.com:new on /mnt/samba/new type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072)

Expected results:
# umount /mnt/samba/new

# mount /mnt/samba/new

# mount | grep new
ad-rhs-srv1.cloud.lab.eng.bos.redhat.com:/new on /mnt/samba/new type fuse.glusterfs (rw,allow_other,max_read=131072)

Notice the difference in the mounted options. If ACL is enabled using setfacl, it fails in the first mounted state but succeeds after manually mounting it. 

Additional info: