And maybe I spent much of today chasing my tail. I decided to just push forward even with those glusterfsd errors in /var/log/messages: gluster peer probe 192.168.253.2 gluster peer status gluster volume create firewall-scripts replica 2 transport tcp 192.168.253.1:/gluster-fw1 192.168.253.2:/gluster-fw2 gluster volume start firewall-scripts mkdir /firewall-scripts mount -t glusterfs 192.168.253.1:/firewall-scripts /firewall-scripts All worked as expected on both nodes. And now when I do Systemctl restart glusterd.service I no longer see those "No such file or directory" errors in /var/log/messages from glusterfsd, just a bunch of SElinux warnings. So apparently, gluster was telling me in its own special way that I did not have any volumes yet. - Greg Scott
