Suse NFS Client unable to get locks, especially after umount / remount

This document (7004439) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 10

SUSE Linux Enterprise Server 10

Situation

A Suse NFS client system is unable to get file locks. In some cases, this may be a client which has been previously getting successful locks. It may even be the case that the original NFS mount was acquiring locks successfully, but after the last (or only) NFS client mount point is dismounted and mounted again, locking fails.

Resolution

In some cases an administrator has mistakenly disabled the "nfsboot" service, so it does not launch upon system boot. This service kicks off sm-notify, which is a requirement of the lockd and statd services which work together to service NFS lock requests and notifications.

This can be checked with the command:

chkconfig -l | grep nfs

If "nfsboot" shows OFF in runlevels 3 and 5, then correct this with:

chkconfig nfsboot 35

This will insure future reboots start the necessary service. To start nfsboot on the fly (before a reboot is possible), use the commands:

rcnfs stop

rcnfsboot start

rcnfs start

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.