archive mirror
 help / color / mirror / Atom feed
From: David Teigland <>
To: Damon Wang <>
Cc: LVM general discussion and development <>
Subject: Re: [linux-lvm] [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
Date: Wed, 27 Jun 2018 09:23:57 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jun 27, 2018 at 10:03:00PM +0800, Damon Wang wrote:
> Hi all,
>   I found duplicate sanlock locks in lvm operation:
>     [root@172-20-11-108 ~]# vgs
>       Duplicate sanlock global locks should be corrected
>       Duplicate sanlock global lock in VG 9e9e5a689750430daff18da75c9718cc
>       Couldn't find device with uuid 7oDKl3-TvVY-Q24z-Q2BC-psUZ-SFCX-j1fhQE.
>       Duplicate sanlock global lock in VG 8c32e39f49024e64832c1bc3fd15f948
>       VG                               #PV #LV #SN Attr   VSize    VFree
>       8c32e39f49024e64832c1bc3fd15f948   4  80   0 wz--ns <291.88g <263.32g
>       9e9e5a689750430daff18da75c9718cc   3  55   0 wz-pns  739.93g <702.65g
>       zstack                             1   2   0 wz--n-  <59.00g       0

> It seems not harmful, but I don't know why it happen.

It can be harmful if different hosts use different global locks.
There's a section in lvmlockd man page about how this happens and
how to correct it.  In short, it happens when you create a new sanlock VG
while the other one is not visible.  To correct it, you disable the global
lock in one of the VGs with 'lvmlockctl --gl-disable <vgname>'.


  reply	other threads:[~2018-06-27 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 14:03 [linux-lvm] [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i" Damon Wang
2018-06-27 14:23 ` David Teigland [this message]
2018-06-27 15:15   ` Damon Wang
2018-06-27 15:26     ` David Teigland
2018-06-27 16:35       ` Damon Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).