From: Zhiyong Ye <yezhiyong@bytedance.com>
To: David Teigland <teigland@redhat.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] vgcreate doesn't work with lvmlockd running
Date: Fri, 6 May 2022 21:27:17 +0800 [thread overview]
Message-ID: <3900d01b-bf36-af1e-013c-2db51c36d8e5@bytedance.com> (raw)
In-Reply-To: <20220505140753.GA30224@redhat.com>
Hi David,
Thanks for your reply and detailed answer. It is true that It works fine
with the latest version of lvm as you said.
Thanks again!
Zhiyong
在 5/5/22 10:07 PM, David Teigland 写道:
> On Thu, May 05, 2022 at 02:08:36PM +0800, Zhiyong Ye wrote:
>> 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)
>
>> 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
>
> This is correct.
>
>> 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.
>
> This looks like a bug, and it does look familiar. I'd guess that section
> of code is missing a call to synchronize with udev (sync_local_dev_names).
> Unfortunately your version of lvm (and sanlock) are old enough that it's
> hard to say immediately if it's fixed. The best option would be trying
> newer versions where it's most likely been fixed.
>
> Dave
>
_______________________________________________
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/
prev parent reply other threads:[~2022-05-09 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 6:08 [linux-lvm] vgcreate doesn't work with lvmlockd running Zhiyong Ye
2022-05-05 14:07 ` David Teigland
2022-05-06 13:27 ` Zhiyong Ye [this message]
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=3900d01b-bf36-af1e-013c-2db51c36d8e5@bytedance.com \
--to=yezhiyong@bytedance.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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).