From: David Teigland <teigland@redhat.com>
To: Gang He <ghe@suse.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: Wed, 17 Oct 2018 09:10:25 -0500 [thread overview]
Message-ID: <20181017141025.GA9941@redhat.com> (raw)
In-Reply-To: <5BC6C5AC020000F90003ACAD@prv1-mh.provo.novell.com>
On Tue, Oct 16, 2018 at 11:16:28PM -0600, Gang He wrote:
> > - allow_changes_with_duplicate_pvs=1
> > - external_device_info_source="udev"
> > - reject sda2, sdb2 in lvm filter
> 1) why did the solution 1 not work? since the method looks more close to
> fix this problem.
Check if the version you are using has this commit:
https://sourceware.org/git/?p=lvm2.git;a=commit;h=09fcc8eaa8eb7fa4fcd7c6611bfbfb83f726ae38
If so, then I'd be interested to see the -vvvv output from that pvs command.
> 2) Could we back-port some code from v2.02.177 source files to keep the
> compatibility? to avoid modifying some items manually. or, we have to
> accept this problem from v2.02.180 (maybe 178?) due to by-design?
It's not clear to me exactly which code you're looking at backporting to
where.
next prev parent reply other threads:[~2018-10-17 14:10 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 [this message]
2018-10-17 18:42 ` David Teigland
2018-10-18 8:51 ` Gang He
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=20181017141025.GA9941@redhat.com \
--to=teigland@redhat.com \
--cc=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).