All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:22:54 +0100	[thread overview]
Message-ID: <VA.000034f0.04225307@news.conactive.com> (raw)
In-Reply-To: <493E7FB1.2090403@redhat.com>

Bryn M. Reeves wrote on Tue, 09 Dec 2008 14:24:49 +0000:

> I also don't really 
> understand why you want to do all this if the data is already on md2.

Maybe I didn't make the problem clear in my first posting.
I created a single member md RAID1 device /dev/md2 on top of /dev/sda3 
(single member because the other disk /dev/sdb3 was holding the data). 
Then I created a PV on /dev/sda3 and a VG on it. I should have done this 
on /dev/md2, though. Small oversight on my part. (I had to recreate that 
array after a complete lowlevel format of the disk and I had the data all 
fine on /dev/sdb3. So I accidentally created the PV on the "counterpart" 
/dev/sda3 instead of the existing raid device.)
Then I moved all the LVs and data back on that PV, added /dev/sdb3 to the 
md device and let it sync. And now I have two identical PVs on both disks 
instead of one PV on the md device.
So, you think pvmove /dev/sda3 /dev/md2 would just do what I want?
Should I break the array and perform the move on the single member array, 
so that I can keep my data on /dev/sdb3 in case something goes wrong?

Kai

-- 
Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com

  reply	other threads:[~2008-12-09 17:23 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 [this message]
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
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.000034f0.04225307@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.