From: "Gang He" <ghe@suse.com>
To: Sven Eschenberg <sven@eschenberg.eu>, teigland@redhat.com
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180
Date: Thu, 18 Oct 2018 02:51:05 -0600 [thread overview]
Message-ID: <5BC84979020000F90003B507@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20181017184204.GC14214@redhat.com>
Hello David,
Thank for your help.
If I include this patch in lvm2 v2.02.180,
LVM2 can activate LVs on the top of RAID1 automatically? or we still have to set "allow_changes_with_duplicate_pvs=1" in lvm.conf?
Thanks
Gang
>>> On 2018/10/18 at 2:42, in message <20181017184204.GC14214@redhat.com>, David
Teigland <teigland@redhat.com> wrote:
> On Wed, Oct 17, 2018 at 09:10:25AM -0500, David Teigland wrote:
>> Check if the version you are using has this commit:
>>
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=09fcc8eaa8eb7fa4fcd7c6611bf
> bfb83f726ae38
>
> I see that this commit is missing from the stable branch:
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=3fd75d1bcd714b02fb2b843d19
> 28b2a875402f37
>
> I'll backport that one.
>
> Dave
next prev parent reply other threads:[~2018-10-18 8:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 10:23 [linux-lvm] Fails to create LVM volume on the top of RAID1 after upgrade lvm2 to v2.02.180 Gang He
2018-10-08 15:00 ` David Teigland
2018-10-15 5:39 ` Gang He
2018-10-15 15:26 ` David Teigland
2018-10-17 5:16 ` Gang He
2018-10-17 14:10 ` David Teigland
2018-10-17 18:42 ` David Teigland
2018-10-18 8:51 ` Gang He [this message]
2018-10-18 16:01 ` David Teigland
2018-10-18 17:59 ` David Teigland
2018-10-19 5:42 ` Gang He
2018-10-23 2:19 ` Gang He
2018-10-23 15:04 ` David Teigland
[not found] ` <59EBFA5B020000E767ECE9F9@prv1-mh.provo.novell.com>
2018-10-24 2:23 ` Gang He
2018-10-24 14:47 ` David Teigland
2018-10-17 17:11 ` Sven Eschenberg
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=5BC84979020000F90003B507@prv1-mh.provo.novell.com \
--to=ghe@suse.com \
--cc=linux-lvm@redhat.com \
--cc=sven@eschenberg.eu \
--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).