From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] vgchange command can not activate mirrored LV in VG
Date: Tue, 17 Jul 2018 01:50:31 -0600 [thread overview]
Message-ID: <5B4D9FC7020000F900029F14@prv1-mh.provo.novell.com> (raw)
Hello List,
I encountered a problem with the source code 2.02.178,
vgchange command did not activate mirrored LV in VG, the error messages were as below,
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
vda 254:0 0 40G 0 disk
├─vda1 254:1 0 4G 0 part [SWAP]
├─vda2 254:2 0 23.6G 0 part /
└─vda3 254:3 0 12.4G 0 part /home
vdb 254:16 0 40G 0 disk
vdc 254:32 0 40G 0 disk
tb0307-nd1:~ # vgchange -aay cluster-vg2
Error locking on node a431337: Shared cluster mirrors are not available. <<= here
2 logical volume(s) in volume group "cluster-vg2" now active
tb0307-nd1:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
vda 254:0 0 40G 0 disk
├─vda1 254:1 0 4G 0 part [SWAP]
├─vda2 254:2 0 23.6G 0 part /
└─vda3 254:3 0 12.4G 0 part /home
vdb 254:16 0 40G 0 disk
└─cluster--vg2-test--lv3 253:1 0 10G 0 lvm
vdc 254:32 0 40G 0 disk
└─cluster--vg2-test--lv 253:0 0 10G 0 lvm
But, I built the lvm2 related rpms with the same code (include configure options ),
vgchange command can work well,
tb0307-nd2:/ # vgchange -aay cluster-vg2
3 logical volume(s) in volume group "cluster-vg2" now active
tb0307-nd2:/ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 3.9G 0 rom /run/media/ghe/openSUSE-Tumbleweed-DVD-x86_6423
vda 254:0 0 40G 0 disk
├─vda1 254:1 0 4G 0 part [SWAP]
├─vda2 254:2 0 23.6G 0 part /
└─vda3 254:3 0 12.4G 0 part /home
vdb 254:16 0 40G 0 disk
├─cluster--vg2-test--lv2_mimage_0 253:2 0 8G 0 lvm
│ └─cluster--vg2-test--lv2 253:4 0 8G 0 lvm
└─cluster--vg2-test--lv3 253:5 0 10G 0 lvm
vdc 254:32 0 40G 0 disk
├─cluster--vg2-test--lv 253:0 0 10G 0 lvm
├─cluster--vg2-test--lv2_mlog 253:1 0 4M 0 lvm
│ └─cluster--vg2-test--lv2 253:4 0 8G 0 lvm
└─cluster--vg2-test--lv2_mimage_1 253:3 0 8G 0 lvm
└─cluster--vg2-test--lv2 253:4 0 8G 0 lvm
Do you know the root cause? what is the possible reason?
Thanks
Gang
reply other threads:[~2018-07-17 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5B4D9FC7020000F900029F14@prv1-mh.provo.novell.com \
--to=ghe@suse.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).