Skip to main content
NetApp Knowledge Base

NFS mount fails when rpc-statd.service is masked on a BeeGFS client

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

BeeGFS cluster with E-Series storage backend

Issue

  • The NFS mount command to access a repository from a BeeGFS client fails only on one node, while it works on other BeeGFS nodes.

    • The affected node reports errors about rpc-statd.service being masked or not running, and NFS access denied by the server.
    • The NFS configuration was reviewed and found identical to working nodes, except rpc-statd.service is disabled/masked on the problematic node.
    Failed to start rpc-statd.service: Unit rpc-statd.service is masked.conf_parse: last line non-terminated, ignored.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: access denied by server while mounting 1.1.1.1:/path/to/export

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.