SUSE Support

Here When You Need Us

During SLES install over NFS, locking is not available

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


SUSE Linux Enterprise Server 10


During a SLES install over NFS, the status daemon (kstatd) is disabled, meaning that NFS file locking cannot be done. While this does not interfere with a standard install, this can cause trouble for those who use autoyast to set up additional customized installation steps, involving NFS mount points beyond the one established for the install source materials.
For example, if an additional NFS mount was done to write data in a remote database during the install, and the client being installed wanted to get locks over that NFS mount, it would fail to get those locks and receive errors.


To workaround this, an NFS mount done during the install procedure can include the 'nolock' parameter. The NFS mount of the install source materials is already done this way. The'nolock' parameter means that when an application on the installing machine asks for a lock, the NFS client code will respond that the lock has been successfully obtained, even though no lock request has actually been sent to the remote NFS server.
This will allow an application which asks for locking to proceed. However, this should be used with caution. If the application is accessing a database that is accessed by multiple clients simultaneously, data loss could occur, since more than one system could think they have locks on certain areas, when they really do not.
If true NFS locking is needed, then the operations in question should be put off until the install is fully complete and the system is rebooted. Note that one reboot already occurs during the install procedure, but an additional reboot after the install is 100% complete will be needed before true locking can be done.


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.

  • Document ID:3544359
  • Creation Date: 19-Jul-2007
  • Modified Date:05-Mar-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.