Chapter 7 Known Issues

The following sections describe known issues in this release.

7.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:

# smbclient -U user%password //node1/gluster-gv1 
tree connect failed: NT_STATUS_UNSUCCESSFUL 

Connecting to a volume using CIFS also fails, for example:

# 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) 

To workaround this, you must do one of the following on the node on which you want to enable Samba access:

  • Set the SELinux samba_load_libgfapi option to 1.

    # setsebool -P samba_load_libgfapi 1
  • Disable enforcing mode on SELinux:

    # setenforce 0

    To make this change permanent, edit the /etc/selinux/config file and change the SELINUX variable to permissive mode.

(Bug 28701091)

7.2 Samba Access Fails on aarch64 Hardware

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 on the aarch64 platform.

(Bug 29048629)