linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zhiyong Ye <yezhiyong@bytedance.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] vgcreate doesn't work with lvmlockd running
Date: Thu, 5 May 2022 14:08:36 +0800	[thread overview]
Message-ID: <8d9bb1b4-9f79-d557-e3d9-2b8e5f53e751@bytedance.com> (raw)

Hi all,

I am new to lvm. When I was trying to create a shared VG (vgcreate
--shared <vg_name> /dev/sdb1 /dev/sdc1) in my system and I received the
"device not cleared" error with sanlock and lvmlockd running. I've
searched the internet but nothing has solved my problem. So I'm here to
ask for your help.

root@n151-143-035:~# lvmlockd -V
lvmlockd version: 2.03.02(2) (2018-12-18)
root@n151-143-035:~# sanlock -V
sanlock 3.6.0 (built Jul 11 2018 12:44:29)

root@n151-143-035:~# systemctl status sanlock
● sanlock.service - Shared Storage Lease Manager
    Loaded: loaded (/lib/systemd/system/sanlock.service; disabled; 
vendor preset: enabled)
    Active: active (running) since Thu 2022-05-05 00:31:17 CST; 11h ago
   Process: 25844 ExecStart=/usr/sbin/sanlock daemon $sanlock_opts 
(code=exited, status=0/SUCCESS)
  Main PID: 25850 (sanlock)
     Tasks: 6 (limit: 6143)
    CGroup: /system.slice/sanlock.service
            ├─25850 /usr/sbin/sanlock daemon -w 0
            └─25852 /usr/sbin/sanlock daemon -w 0
May 05 00:31:17 n151-143-035 systemd[1]: Starting Shared Storage Lease 
Manager...
May 05 00:31:17 n151-143-035 systemd[1]: Started Shared Storage Lease 
Manager.

root@n151-143-035:~# systemctl status lvmlockd
● lvmlockd.service - LVM lock daemon
    Loaded: loaded (/lib/systemd/system/lvmlockd.service; enabled; 
vendor preset: enabled)
    Active: active (running) since Thu 2022-05-05 00:31:23 CST; 11h ago
      Docs: man:lvmlockd(8)
  Main PID: 26152 (lvmlockd)
     Tasks: 3 (limit: 6143)
    CGroup: /system.slice/lvmlockd.service
            └─26152 /sbin/lvmlockd --foreground
May 05 00:31:23 n151-143-035 systemd[1]: Starting LVM lock daemon...
May 05 00:31:23 n151-143-035 lvmlockd[26152]: [D] creating 
/run/lvm/lvmlockd.socket
May 05 00:31:23 n151-143-035 lvmlockd[26152]: 1651681883 lvmlockd started
May 05 00:31:23 n151-143-035 systemd[1]: Started LVM lock daemon.

root@n151-143-035:~# pvs
   Skipping global lock: lockspace not found or started
root@n151-143-035:~# pvcreate /dev/mapper/mpatha1
   Global lock failed: check that global lockspace is started
root@n151-143-035:~# pvs
   Skipping global lock: lockspace not found or started

It is mentioned in the main page under "creating the first sanlock VG"
that the first VG is created to get the global lock, so I create the VG
directly:

root@n151-143-035:~# vgcreate --lock-type sanlock --shared test 
/dev/mapper/mpatha1 --verbose
   Enabling sanlock global lock
     Wiping signatures on new PV /dev/mapper/mpatha1.
     Set up physical volume for "/dev/mapper/mpatha1" with 2147483648 
available sectors.
     Zeroing start of device /dev/mapper/mpatha1.
     Writing physical volume data to disk "/dev/mapper/mpatha1".
   Physical volume "/dev/mapper/mpatha1" successfully created.
     Adding physical volume '/dev/mapper/mpatha1' to volume group 'test'
     Archiving volume group "test" metadata (seqno 0).
     Creating logical volume lvmlock
     Creating volume group backup "/etc/lvm/backup/test" (seqno 2).
     Activating logical volume test/lvmlock.
     activation/volume_list configuration setting not defined: Checking 
only host tags for test/lvmlock.
     Creating test-lvmlock
     Loading table for test-lvmlock (254:1).
     Resuming test-lvmlock (254:1).
   /dev/test/lvmlock: not found: device not cleared
   Aborting. Failed to wipe start of new LV.
     Removing test-lvmlock (254:1)
     Creating volume group backup "/etc/lvm/backup/test" (seqno 3).
   Failed to create sanlock lv lvmlock in vg test
   Failed to create internal lv.
   Failed to initialize lock args for lock type sanlock
     Removing physical volume "/dev/mapper/mpatha1" from volume group "test"
   Volume group "test" successfully removed
root@n151-143-035:~# pvs
   Skipping global lock: lockspace not found or started
   PV                  VG Fmt  Attr PSize PFree
   /dev/mapper/mpatha1    lvm2 ---  1.00t 1.00t
root@n151-143-035:~# vgs
   Skipping global lock: lockspace not found or started

I set use_lvmlockd = 1 in the configuration file /etc/lvm/lvm.conf and
did not find useful log information in /var/log/syslog and /var/log
/sanlock.log. And I can successfully use and create lvm when
use_lvmlockd = 0.

Regards,

Zhiyong Ye

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

             reply	other threads:[~2022-05-05  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  6:08 Zhiyong Ye [this message]
2022-05-05 14:07 ` David Teigland
2022-05-06 13:27   ` Zhiyong Ye

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=8d9bb1b4-9f79-d557-e3d9-2b8e5f53e751@bytedance.com \
    --to=yezhiyong@bytedance.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] vgcreate doesn'\''t work with lvmlockd running' \
    /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

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).