Shulou(Shulou.com)06/01 Report--

This article mainly introduces "how to solve the problem that CentOS cannot mount Glusterfs". In daily operation, I believe many people have doubts about how to solve the problem that CentOS cannot mount Glusterfs. Xiaobian consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubt that "how to solve the problem that CentOS can not mount Glusterfs"! Next, please follow the editor to study!

Solution:

Mount command executed:

Mount target_host:/volume_name current_path

An error message is prompted after executing the mount command

/ 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

In general, the places where Glusterfs storage is used are configured by at least two machines, and the corresponding services can be started normally on their respective machines. However, when you execute the gluster volume info command to view the defined volume information, you will find that the machine state that is not stored locally is offline. When you do mount locally or elsewhere, you will not be successful and will prompt 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. Check the iptables configuration of each machine, back up the previous iptables configuration (/ etc/sysconfig/iptables), then export the effective iptables (service iptables save), check whether the existing configuration is different from the pre-export configuration, repair it, and finally restart the iptables service (service iptables restart).

2. Check whether the IP configuration of each machine has changed (ifconfig) and whether it is the same network segment. If there is a change in the configuration, change it back to the original configuration and restart the network service (service network restart).

After the above network problems are solved, execute mount target_host:/volume_name current_path again (generally, the parameter-t glusterfs is not required) to mount the volume managed by gluster. At this time, if the mount fails, add the-t parameter, that is, mount-t glusterfs target_host:/volume_name current_path.

The above is an introduction to the reasons and solutions for the failure of CentOS to mount Glusterfs. After this problem occurs, you might as well check the network configuration between the machines.

At this point, the study on "how to solve the problem that CentOS cannot mount Glusterfs" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.