The reason and solution of Glusterfs in CentOS under the condition of being unable to mount

Mount command to execute:

Mount Target_host:/volume_name Current_path

Prompt for error message after executing mount command

/usr/sbin/start-statd:line 8:systemctl:command not found

MOUNT.NFS:RPC.STATD is isn't running but is required for remote locking.

Mount.nfs:Either use '-o nolock ' to keep locks the local, or start statd.

Mount.nfs:Operation not permitted

In general, the use of glusterfs storage is at least two machines configured to complete, on their respective machines can normally start the corresponding service; However, when you perform the Gluster volume Info command to view the defined volume information, You will find that the machine state of the non-native storage is offline, at which point the mount will not succeed either locally or elsewhere, prompting timeout (link timeout)-This is the problem (the network is not smooth);

At this point, you need to deal with the network configuration between machines, here are two points:

1, look at the iptables configuration of each machine, backup before the iptables configuration (/etc/sysconfig/iptables), and then export the effective iptables (service iptables Save), Check to see if there are any differences between existing and exported configurations, fix it, and restart Iptables service (iptables restart);

2, to see whether the IP configuration of each machine changes (ifconfig), whether the same network segment, if the configuration changes, then change back to the original configuration, restart Network Services (service network restart);

Once the above network problem is resolved, the Mount Target_host:/volume_name Current_path (generally do not need parameter-T glusterfs) is executed again to complete the mount of volume managed by Gluster; if Mount fails, Plus-T parameter, that is, mount-t glusterfs target_host:/volume_name Current_path