Reading VG without a lock

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

Environment

SUSE Linux Enterprise High Availability Extension 15

Situation

In a cluster environment with a clustered logical volume, pvs, vgs and lvs might report the following error: 
 
Reading VG <VG_NAME> without a lock

Resolution

To fix above issue: 
  1. both nodes should be online and maintenance is off 
  2. cluster should not be in maintenance mode 
  3. run: "vgchange --lockstart" on both nodes 

Cause

In a cluster environment locking is getting provided using DLM.
When putting a node in maintenance mode and then rebooting, the node will not acquire all needed locks unless resource failover or running above vgchange command.
This can be checked by using: dlm_tool ls

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.

  • Document ID:000019914
  • Creation Date: 16-Mar-2021
  • Modified Date:16-Mar-2021
    • SUSE Linux Enterprise High Availability Extension

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

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

Join Our Community

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.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

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

Go to Customer Center