From: Damon Wang <damon.devops@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i"
Date: Wed, 27 Jun 2018 22:03:00 +0800 [thread overview]
Message-ID: <CABZYMH6HdrtYOb-eu1VOfUAMv+OqzzuP3VBviZLX=2M5WJTX-g@mail.gmail.com> (raw)
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
while lvmlockctl -i:
[root@172-20-11-108 ~]# lvmlockctl -i
VG 8c32e39f49024e64832c1bc3fd15f948 lock_type=sanlock
npweb0-UQs8-hviS-PA8L-mOgI-eMDO-qY5OpK
LS sanlock lvm_8c32e39f49024e64832c1bc3fd15f948
LK VG un ver 229
LK GL un ver 1
LK LV un nvnmw0-WMeY-nm4V-zEfl-Dcpc-bGJr-rL8gpG
LK LV sh hGVNWa-wwFx-SsQJ-Y6t4-UvPJ-CKEq-1CICng
LK LV ex YtvSmz-Mo7H-gQnV-QfLp-Pb9P-HXpO-Fw3iDZ
... ...
LK LV ex sUUEqr-B38J-Cktj-fky0-g5he-xS3o-wq9Lor
LK LV ex k943Uw-du21-EOg0-F1t5-NKrH-aPof-Wt37Mi
VG 9e9e5a689750430daff18da75c9718cc lock_type=sanlock
JBTlB1-fjbM-YpOc-6Qnt-Spxj-nEM4-oQaBCT
LS sanlock lvm_9e9e5a689750430daff18da75c9718cc
LK VG un ver 208
LK LV sh rnb8Lc-XbBu-dqPn-kfNC-SsW4-F9KF-nK6fsu
LK LV un YftJt5-1G9S-0icO-HkbU-7vqL-OPrZ-ppO8WO
It seems not harmful, but I don't know why it happen.
Thanks,
Damon
next reply other threads:[~2018-06-27 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 14:03 Damon Wang [this message]
2018-06-27 14:23 ` [linux-lvm] [lvmlockd] "Duplicate sanlock global locks" warned but not found in "lvmlockctl -i" David Teigland
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABZYMH6HdrtYOb-eu1VOfUAMv+OqzzuP3VBviZLX=2M5WJTX-g@mail.gmail.com' \
--to=damon.devops@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).