From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: list@xenhideout.nl
Subject: Re: [linux-lvm] how to change UUID of PV of duplicate partition (followup)
Date: Fri, 6 Jan 2017 21:06:17 +0100 [thread overview]
Message-ID: <88a5fbe3-0806-ac5f-7da2-0555fc6d3ff7@redhat.com> (raw)
In-Reply-To: <6191529afb210ae7042670822f5fe1ad@xenhideout.nl>
Dne 6.1.2017 v 20:21 Xen napsal(a):
> David Teigland schreef op 06-01-2017 20:19:
>> On Fri, Jan 06, 2017 at 08:10:20PM +0100, Xen wrote:
>>> This is what I mean:
>>>
>>> Found duplicate PV 3U9ac3Ah5lcZUf03Iwm0cgMMaKxdflg0: using /dev/sdb4 not
>>> /dev/sdc4
>>
>> The handling of duplicate PVs has been entirely redone in recent versions.
>> The problems you are having are well known and should now be fixed.
>
> Oh right, I was going to write my LVM version, but did not manage to produce
> it yet, sorry :p.
>
> Good to know. Yeah I am using 16.04 from Ubuntu's version.
>
> LVM version: 2.02.133(2) (2015-10-30)
> Library version: 1.02.110 (2015-10-30)
> Driver version: 4.34.0
>
> Sigh... I guess I'll have to make some time to start using a recent version
> then on this system. Perhaps it was due time. Always these old versions...
>
> _______________________________________________
You can always 'fix it' you way.
Just setup device filter in lvm.conf so you either see diskA or diskB
In you particular case:
filter = [ "r|/dev/sdb4|" ]
or
filter = [ "r|/dev/sdc4|" ]
And set/change things with your existing lvm2 version....
Regards
Zdenek
next prev parent reply other threads:[~2017-01-06 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 19:10 [linux-lvm] how to change UUID of PV of duplicate partition (followup) Xen
2017-01-06 19:19 ` David Teigland
2017-01-06 19:21 ` Xen
2017-01-06 20:06 ` Zdenek Kabelac [this message]
2017-01-06 20:13 ` Xen
2017-01-06 20:11 ` Xen
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=88a5fbe3-0806-ac5f-7da2-0555fc6d3ff7@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=list@xenhideout.nl \
/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).