[linux-lvm] [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
Damon Wang
damon.devops at gmail.com
Wed Jun 27 15:15:03 UTC 2018
Hi,
Thank you for your reply.
I’m wonder why I see only one global lock in lvmlockctl -i, should I got multiple gl lock in lvmlock -i when it warn “duplicate gl lock”?
Thanks!
Damon
> 在 2018年6月27日,下午10:23,David Teigland <teigland at redhat.com> 写道:
>
>> On Wed, Jun 27, 2018 at 10:03:00PM +0800, Damon Wang wrote:
>> Hi all,
>>
>> I found duplicate sanlock locks in lvm operation:
>>
>> [root at 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>'.
>
> Dave
More information about the linux-lvm
mailing list