[Gluster-devel] is_nfs_export_available from nfs.rc failing too often?

Jiffin Thottan jthottan at redhat.com
Wed Apr 3 06:26:20 UTC 2019


is_nfs_export_available is just a wrapper around "showmount" command AFAIR.
I saw following messages in console output.
 mount.nfs: rpc.statd is not running but is required for remote locking.
05:06:55 mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
05:06:55 mount.nfs: an incorrect mount option was specified

For me it looks rpcbind may not be running on the machine.
Usually rpcbind starts automatically on machines, don't know whether it can happen or not. 


----- Original Message -----
From: "Atin Mukherjee" <amukherj at redhat.com>
To: "gluster-infra" <gluster-infra at gluster.org>, "Gluster Devel" <gluster-devel at gluster.org>
Sent: Wednesday, April 3, 2019 10:46:51 AM
Subject: [Gluster-devel] is_nfs_export_available from nfs.rc failing too	often?

I'm observing the above test function failing too often because of which arbiter-mount.t test fails in many regression jobs. Such frequency of failures wasn't there earlier. Does anyone know what has changed recently to cause these failures in regression? I also hear when such failure happens a reboot is required, is that true and if so why? 

One of the reference : https://build.gluster.org/job/centos7-regression/5340/consoleFull 

Gluster-devel mailing list
Gluster-devel at gluster.org

More information about the Gluster-devel mailing list