From: Kai Schaetzl <maillists@conactive.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] shift PV from disk to raid device?
Date: Tue, 09 Dec 2008 20:42:54 +0100 [thread overview]
Message-ID: <VA.000034f7.04a27ead@news.conactive.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0812091325290.17327@bmsred.bmsi.com>
Stuart D. Gathman wrote on Tue, 9 Dec 2008 13:38:46 -0500 (EST):
> 1) create md2 from sda3 and sdb3
> 2) pvcreate md2
> 3) add sda3 to VG - LVM complains about dup and uses sdb3 instead
A bit different. But thanks for this hint. I checked my bash history now.
Short summary:
mdadm --create --verbose /dev/md3 --level=1 --raid-devices=2 /dev/sda3 missing
mdadm --detail /dev/md3
pvcreate /dev/md3
pvcreate /dev/md3 -ff
vgcreate dom1 /dev/md3 (to avoid name clash with dom0 on sdb3)
.. some lvcreate and other stuff
mdadm --detail /dev/md3
reboot
vgchange dom1 -an
vgrename dom1 dom0
vgchange dom0 -ay
mdadm /dev/md3 -a /dev/sdb3
reboot
So, I did it all alright. I was wrong with my assumption about using the wrong
device for the PV. However, I only notice now that /dev/md3 is gone for good,
mdadm cannot find it. I had not been paying attention and thought that md2 was
the array in question. (Thinking md0=sda1/sdb1, md1=sda2/sdb2, md2=sda3/sdb3, but
I used md0=sda1/sdb1, md2=sda2/sdb2, md3=sda3/sdb3). So I didn't notice it.
Going further back in the history, it seems I forgot to pvremove the earlier
existing PV /dev/sda3 (which had the same structure and data) before creating the
PV on /dev/md3. That's why I had to -ff /dev/md3 I assume. It seems that after
adding sdb3 to the array and rebooting the array dissolved completely and the
existing PVs on sda3 and sdb3 came back into existence. And I thought it was an
effect of the mirror sync.
So, I think I will just start over by removing /dev/sda3 now completely,
recreating the raid array and then recreating the PV on it. I think I should then
be able to pvmove the LVs from /dev/sdb3 to /dev/md3, right? Problem solved. This
time.
However, as this is the second time that this or a similar array just vanishes I
wonder if there's something else going on. e.g. some kind of unwanted interaction
between LVM and mdraid partitions. The other two raid arrays on the disk are
absolutely stable and don't use LVM.
Kai
--
Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.co
next prev parent reply other threads:[~2008-12-09 19:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 23:41 [linux-lvm] shift PV from disk to raid device? Kai Schaetzl
2008-12-09 10:30 ` Bryn M. Reeves
2008-12-09 13:09 ` Kai Schaetzl
2008-12-09 14:24 ` Bryn M. Reeves
2008-12-09 17:22 ` Kai Schaetzl
2008-12-09 16:54 ` Stuart D. Gathman
2008-12-09 16:56 ` Stuart D. Gathman
2008-12-09 17:36 ` Bryn M. Reeves
2008-12-09 18:16 ` Kai Schaetzl
2008-12-09 18:32 ` Kai Schaetzl
2008-12-09 18:03 ` Kai Schaetzl
2008-12-09 18:06 ` Bryn M. Reeves
2008-12-09 18:20 ` Kai Schaetzl
2008-12-09 18:38 ` Stuart D. Gathman
2008-12-09 19:42 ` Kai Schaetzl [this message]
2008-12-09 19:56 ` Doug Ledford
2008-12-09 20:15 ` Kai Schaetzl
2008-12-09 20:22 ` Doug Ledford
2008-12-09 21:03 ` Stuart D. Gathman
2008-12-09 21:22 ` Doug Ledford
2008-12-09 20:38 ` Kai Schaetzl
2008-12-09 20:51 ` Doug Ledford
2008-12-09 21:04 ` Stuart D. Gathman
2008-12-09 20:49 ` Kai Schaetzl
2008-12-09 20:56 ` Doug Ledford
2008-12-10 0:31 ` Kai Schaetzl
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=VA.000034f7.04a27ead@news.conactive.com \
--to=maillists@conactive.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 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.