From: David Teigland <teigland@redhat.com>
To: Neutron Sharc <neutronsharc@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] new multipath device mistakenly replaced another PV in existing volume group
Date: Thu, 20 Apr 2017 11:24:11 -0500 [thread overview]
Message-ID: <20170420162411.GC29033@redhat.com> (raw)
In-Reply-To: <20170420160432.GB29033@redhat.com>
On Thu, Apr 20, 2017 at 11:04:32AM -0500, David Teigland wrote:
> On Wed, Apr 19, 2017 at 02:53:19PM -0700, Neutron Sharc wrote:
> > Please note that all these vol3_[0-3] are fresh, without any LVM
> > metadata on them, as shown by pvscan::
> > sudo pvscan --cache /dev/mapper/vol3_0
> > Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096
> > Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096
> > Incorrect metadata area header checksum on /dev/mapper/vol3_0 at offset 4096
>
> That error indicates there is LVM metadata on them.
>
> > Found duplicate PV 9F6vU9NVBfEq1w3e04T5UreO6fDVPJNy: using
> > /dev/mapper/vol1_3 not /dev/mapper/vol3_0
>
> That error indicates it's the same LVM metadata on them.
>
> Perhaps you're exporting the same data source on the back end via separate
> devices, or have copied the data sources, or are using snapshots of them.
Also, if you upgrade to a new version of lvm, there is better checking and
reporting for these conditions.
next prev parent reply other threads:[~2017-04-20 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 21:53 [linux-lvm] new multipath device mistakenly replaced another PV in existing volume group Neutron Sharc
2017-04-20 16:04 ` David Teigland
2017-04-20 16:24 ` David Teigland [this message]
2017-04-22 2:13 ` Neutron Sharc
[not found] <971194068.8176464.1492969500597.ref@mail.yahoo.com>
2017-04-23 17:45 ` matthew patton
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=20170420162411.GC29033@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=neutronsharc@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.