Causes and solutions for failure to mount glusterfs in CentOS

Causes and solutions for failure to mount glusterfs in CentOS

Run the mount command:

Mount target_host:/volume_name current_path

After the mount command is executed, an error message is displayed.

/Usr/sbin/start-statd: line 8: systemctl: command not found
Mount. nfs: rpc. statd is not running but is required for remote locking.
Mount. nfs: Either use '-o nolock' to keep locks local, or start statd.
Mount. nfs: Operation not permitted

Generally, the glusterfs storage is configured on at least two machines, and the corresponding services can be started on the respective machines. However, when you execute the gluster volume info command to view the defined volume information, you will find that the status of machines not stored on the local machine is offline. In this case, the machine will not succeed when mounting is performed locally or elsewhere, the system will prompt timeout (link timeout) -- this is the problem (the network is not smooth );

At this time, you need to process the network configuration between machines. Here there are two points:

1. view the iptables configuration of each machine, back up the previous iptables configuration (/etc/sysconfig/iptables), and export the effective iptables (service iptables save ), check whether the existing configuration is different from that before export. If yes, fix the problem. restart the iptables service (iptables restart );

2. Check whether the IP address configuration of each machine has changed (ifconfig) and the same network segment. If the configuration changes, change the original configuration and restart the network service (service network restart );

After the preceding network problem is solved, mount target_host:/volume_name current_path (the-t glusterfs parameter is not required) to mount the volume managed by gluster. If the mounting fails, the-t parameter is added, that is, mount-t glusterfs target_host:/volume_name current_path.