To set up the volume for Samba access:

On each node in the trusted storage pool on which you want to enable Samba access:

1. Install the Samba packages for Gluster:

   # yum install samba samba-vfs-glusterfs

2. If you are running a firewall service, enable access to Samba on the node. For example:

   # firewall-cmd --permanent --add-service=samba 
   # firewall-cmd --reload

3. Enable and start the Samba service:

   # systemctl enable --now smb

4. (Optional) If you do not have an authentication system configured (for example, an LDAP server), you can create a Samba user to enable access to the Samba share from clients. This user should be created on all nodes set up to export the Samba share. For example:

   # adduser myuser
   # smbpasswd -a myuser
   New SMB password:
   Retype new SMB password:
   Added user myuser.

   Restart the Samba service:

   # systemctl restart smb

5. (Optional) If you want to allow guest access to a Samba share (no authentication is required), add a new line containing map to guest = Bad User to the [global] section of the /etc/samba/smb.conf file on each node set up to export the Samba share. For example:

   [global]
          workgroup = SAMBA
          security = user
   
          passdb backend = tdbsam
   
          printing = cups
          printcap name = cups
          load printers = yes
          cups options = raw
          map to guest = Bad User

   Allowing guest access also requires that the [gluster-volume_name] section contains the guest ok = yes option, which is set automatically with the Gluster hook scripts in the next step.

   Restart the Samba service:

   # systemctl restart smb

6. If you have a running Gluster volume, stop it and start it again. On any node in the trusted storage pool, run:

   # gluster volume stop myvolume
   # gluster volume start myvolume

   When you start a Gluster volume, a Gluster hook is triggered to automatically add a configuration entry for the volume to the /etc/samba/smb.conf file on each node, and to reload the Samba service. This script generates a Samba configuration entry similar to the following:

   [gluster-myvolume]
   comment = For samba share of volume myvolume
   vfs objects = glusterfs
   glusterfs:volume = myvolume
   glusterfs:logfile = /var/log/samba/glusterfs-myvolume.%M.log
   glusterfs:loglevel = 7
   path = /
   read only = no
   guest ok = yes
   kernel share modes = no

   Note

   The value of the [gluster-myvolume] entry sets the name you use to connect to the Samba share in the connection string.

7. (Optional) If you do not want Gluster to automatically configure Samba to export shares for Gluster volumes, you can remove or rename the hook scripts that control this behavior. On each node on which you want to disable the Samba shares, rename the hook scripts, for example:

   # rename S30 disabled-S30 $(find /var/lib/glusterd -type f -name S30samba*)

   To re-enable the hooks, you can run:

   # rename disabled-S30 S30 $(find /var/lib/glusterd -type f -name *S30samba*)

8. Disable enforcing mode on SELinux for any node where you have set up Samba access:

   # setenforce 0

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

To test access to the volume using SMB:

1. On an Oracle Linux host, install the Samba client package:

   # yum install samba-client

2. Use the smbclient command to list Samba shares on a node in the trusted storage pool where you set up Samba. For example:

   # smbclient -N -U% -L node1

   To look directly at the contents of the volume, you can do:

   # smbclient -N -U% //node1/gluster-myvolume -c ls

   In this command, you specify the Samba share name for the Gluster volume. This name can be found on a host where you set up the Samba share, in the /etc/samba/smb.conf file. Usually the Samba share name is gluster-volume_name.

To test access to the volume using CIFS:

1. On an Oracle Linux host, install the cifs-utils package:

   # yum install cifs-utils

2. Create a mount directory where you intend to mount the volume. For example:

   # mkdir /gluster-storage

3. Mount the volume on the directory using the cifs mount type and by specifying a node within the pool, along with the Samba share name for the Gluster volume. This name can be found on a host where you set up the Samba share, in the /etc/samba/smb.conf file. Usually the Samba share name is gluster-volume_name. For example:

   # mount -t cifs -o guest //node1/gluster-myvolume /gluster-storage

   If you have set up the volume to enable mounting a subdirectory, you can add the subdirectory name to the path on the Gluster file system:

   # mount -t cifs -o guest //node1/gluster-myvolume/subdirectory /gluster-storage

   If you want to pass authentication credentials to the Samba share, first add them to a local file. In this example, the credentials are saved to the file /credfile.

   username=value
   password=value

   Set the permissions on the credentials file so other users cannot access it.

   # chmod 600 /credfile

   You can then use the credentials file to connect to the Samba share, for example:

   # mount -t cifs -o credentials=/credfile //node1/gluster-myvolume /gluster-storage

4. Check the permissions on the new mount to make sure the appropriate users can read and write to the storage. For example:

   # chmod 777 /gluster-storage