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 14:09:26 +0100 [thread overview]
Message-ID: <VA.000034ed.033a3e5f@news.conactive.com> (raw)
In-Reply-To: <493E48DE.3070705@redhat.com>
Bryn M. Reeves wrote on Tue, 09 Dec 2008 10:30:54 +0000:
I notice that I wrote "/dev/sda" where I should have written "/dev/sda3",
of course. But I guess this doesn't make a difference.
> pvmove
thank you. I remember this command from reading the LVM how-to some months
ago, but had forgotten by now. I had checked the pvchange command, but not
this one. After reading man pvmove I'm not sure if using that would really
be helpful. If I understand correctly using it will still copy a lot of
data (all the data on the LVs). Basically it seems to move out all data
from dev/sdan to a temporary lv, then move them back in to /dev/mdn. From
my non-expert view this might create a quite "unfavorable" data layout as
it is all happening within the same "data location" on the disk. And all
in all it might also take longer than a brute-force approach. I had hoped
there's some way to just move lvm metadata so that it knows it belongs to
/dev/mdn and not /dev/sdan anymore.
So, I wonder if it isn't as good or even better if I do the following:
- break the raid array md2
(made from /dev/sda3 and /dev/sdb3 with duplicate PVs)
- remove the PV on /dev/sda3
- recreate it and all LVs on /dev/md2
- copy over the data from the LVs on /dev/sdb3
?
Kai
--
Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
next prev parent reply other threads:[~2008-12-09 13:09 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 [this message]
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
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.000034ed.033a3e5f@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.