Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
Centos 7 latest
glusterfs-api-3.6.9-1.el7.x86_64
glusterfs-server-3.6.9-1.el7.x86_64
glusterfs-libs-3.6.9-1.el7.x86_64
glusterfs-3.6.9-1.el7.x86_64
glusterfs-cli-3.6.9-1.el7.x86_64
glusterfs-fuse-3.6.9-1.el7.x86_64
samba-vfs-glusterfs-4.2.3-11.el7_2.x86_64
samba-libs-4.2.3-11.el7_2.x86_64
samba-client-libs-4.2.3-11.el7_2.x86_64
samba-vfs-glusterfs-4.2.3-11.el7_2.x86_64
samba-common-tools-4.2.3-11.el7_2.x86_64
samba-common-libs-4.2.3-11.el7_2.x86_64
samba-4.2.3-11.el7_2.x86_64
samba-common-4.2.3-11.el7_2.noarch
How reproducible:
On demand
Steps to Reproduce:
1.Setup GlusterFS / Samba configuration as per documentation provided for Gluster 3.0 / 3.1 https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/sect-SMB.html
2. Attempt to mount samba share from client (mount -t cifs -o guest,sec=none //gluster2/gluster-mythinvol1 /mnt/samba/mythinvol1)
Actual results:
Samba share is not mountable due to error between samba and gluster
[root@glusterclient1 ~]# mount -t cifs -o guest,sec=none //gluster2/gluster-mythinvol1 /mnt/samba/mythinvol1/
mount error(13): Permission denied
Expected results:
Samba share is mounted
Additional info:
Error log
==> /var/log/samba/log.glusterclient1 <==
[2016/03/07 16:37:08.250984, 0] ../source3/modules/vfs_glusterfs.c:257(vfs_gluster_connect)
mythinvol1: Initialized volume from server localhost
[2016/03/07 16:37:08.260580, 2] ../source3/smbd/service.c:862(make_connection_snum)
glusterclient1 (ipv4:192.168.0.121:39139) connect to service gluster-mythinvol1 initially as user nobody (uid=99, gid=99) (pid 28656)
[2016/03/07 16:37:10.848514, 2] ../source3/smbd/vfs.c:1240(check_reduced_name)
check_reduced_name: Bad access attempt: * is a symlink outside the share path
conn_rootdir =/
resolved_name=/./*
[2016/03/07 16:39:25.076492, 2] ../source3/smbd/service.c:1138(close_cnum)
glusterclient1 (ipv4:192.168.0.121:39139) closed connection to service gluster-mythinvol1
To fix this error i added global configuration to /etc/samba/smb.conf and restarted smb
follow symlinks = yes
wide links = yes
unix extensions = no
After which following command works
[root@glusterclient1 ~]# mount -t cifs -o guest,sec=none //gluster2/gluster-mythinvol1 /mnt/samba/mythinvol1/
└─/mnt/samba/mythinvol1 //gluster2/gluster-mythinvol1
cifs rw,relatime,vers=1.0,cache=strict,domain=GLUSTER2,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.0.112,file_mode=0755,dir_mode=0755,nounix,serverino,rsi
Additionally i found an error information describing this from Samba https://attachments.samba.org/attachment.cgi?id=11744
Seems to me without these parameters either documented or defaults and according to documentation the functionality does not work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2468.html