Chapter 8 Known Issues
The following sections describe known issues in this release.
8.1 Samba Access Fails with SELinux Enabled
If a node in the trusted storage pool on which you want to enable Samba access has SELinux enabled, Samba clients fail to connect to the volume, using both SMB and CIFS.
Connecting to a volume using SMB fails, for example:
sudo smbclient -U user%password //node1/gluster-gv1
tree connect failed: NT_STATUS_UNSUCCESSFUL
Connecting to a volume using CIFS also fails, for example:
sudo mount -t cifs -o guest //node1/gluster-gv1 /mnt/glusterfs/
mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
As a workaround, set the samba_load_libgfapi
parameter on the node on which you want to enable Samba access:
sudo setsebool -P samba_load_libgfapi 1
(Bug 28701091)
8.2 Samba Access Fails
Samba clients fail to connect to a Gluster volume, using both SMB
and CIFS. This is due to the unavailability of the
samba-vfs-glusterfs package. This issue is
encountered on both x86_64 and aarch64 Oracle Linux 8 systems. On Oracle Linux 7
systems, the issue is encountered only on aarch64 platforms.
As a workaround in the absence of the
samba-vfs-glusterfs package, you can mount the
volume by using FUSE, which is the Gluster native mount, in the
same system where the Samba server is running. Then you would
share the mount point by using the Samba server.
(Bugs 29048629; 30205755)