linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: teigland@redhat.com
Cc: Sven Eschenberg <sven@eschenberg.eu>, 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: Tue, 23 Oct 2018 20:23:06 -0600	[thread overview]
Message-ID: <5BCFD78A020000F90003C8CA@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <59EBFA5B020000E767ECE9F9@prv1-mh.provo.novell.com>

Hello David,

I am sorry, I can not understand your reply quickly.

>>> On 2018/10/23 at 23:04, in message <20181023150436.GB8413@redhat.com>, David
Teigland <teigland@redhat.com> wrote:
> On Mon, Oct 22, 2018 at 08:19:57PM -0600, Gang He wrote:
>>   Process: 815 ExecStart=/usr/sbin/lvm pvscan --cache --activate ay 9:126 
> (code=exited, status=5)
>> 
>> Oct 22 07:34:56 linux-dnetctw lvm[815]:   WARNING: Not using device 
> /dev/md126 for PV qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV.
>> Oct 22 07:34:56 linux-dnetctw lvm[815]:   WARNING: PV 
> qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV prefers device /dev/sdb2 because 
> of previous preference.
>> Oct 22 07:34:56 linux-dnetctw lvm[815]:   Cannot activate LVs in VG vghome 
> while PVs appear on duplicate devices.
> 
> I'd try disabling lvmetad, I've not been testing these with lvmetad on.
your means is, I should let the user disable lvmetad? 

> We may need to make pvscan read both the start and end of every disk to
> handle these md 1.0 components, and I'm not sure how to do that yet
> without penalizing every pvscan.
What can we do for now? it looks there needs add more code implement this logic.

Thanks
Gang

> 
> Dave

  parent reply	other threads:[~2018-10-24  2:23 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
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 [this message]
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=5BCFD78A020000F90003C8CA@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).