From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: oliver_block2@web.de
Subject: Re: [linux-lvm] Duplicate physical volumes
Date: Tue, 27 Aug 2013 12:37:02 +0200 [thread overview]
Message-ID: <521C814E.1050908@redhat.com> (raw)
In-Reply-To: <trinity-3825ffd4-bc3f-4b3d-b3b8-b0feb9436f1f-1377430137079@3capp-webde-bs10>
Dne 25.8.2013 13:28, oliver_block2@web.de napsal(a):
> Dear LVM list,
> this is my first posting to this list and actually I am making my first
> experiences with LVM. The following is my situation:
> I had a RAID 1 consisting of /dev/sdb1 and /dev/sdc1 making /dev/md2 and used
> this device as a physical volume for LVM. I used this inside the volume group
> vg_data.
> Now I decided to convert this RAID 1 into a RAID 5 by "adding a third and
> identical partition /dev/sdd1". It follows how I am going to realize this:
> First I removed /dev/sdc1 from /dev/md2 (the old RAID 1) leaving it in
> degraded state.
> Then I created a new RAID 5, having device name /dev/md0 with a total of three
> disks, but running only with two disks for the moment, namely /dev/sdc1 and
> /dev/sdd1.
> The plan is now to initialize /dev/md0 as a physical volume and add a volume
> group and logical volume on top of this. Then I would copy the data from the
> old RAID 1 to the new RAID 5. Finally I will remove the old RAID 1 and add the
> remaining device /dev/sdb1 to the new RAID 5. Then the conversion would be
> complete.
> Now the actual problem related to LVM:
You need to make sure you have proper filter rules set in lvm.conf.
> While trying to initialize the new /dev/md0 as a pysical volume for LVM, I get
> the following message:
> # pvcreate /dev/md0
> Incorrect metadata area header checksum on /dev/md0 at offset 3000456183808
> Found duplicate PV LNqPKpqdtqcLkmiqHYOeeVddNYx7FDOq: using /dev/md2 not
> /dev/md0
> Can't initialize physical volume "/dev/md0" of volume group "vg_data"
> without -ff
When you are destroying previous raids - you should properly wipe disk
headers. Otherwise you need to use force options to overwrite existing one,
with the risk you could do more damage if you are not 100% what you are doing.
Zdenek
next prev parent reply other threads:[~2013-08-27 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 11:28 [linux-lvm] Duplicate physical volumes oliver_block2
2013-08-27 10:37 ` Zdenek Kabelac [this message]
[not found] ` <521BAF57.5050709@gathman.org>
2013-08-29 16:21 ` Stuart D. Gathman
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=521C814E.1050908@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=oliver_block2@web.de \
/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).