All of lore.kernel.org
 help / color / mirror / Atom feed
From: Farkas Levente <lfarkas@bppiac.hu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] is it possible to move lvm2 logvols?
Date: Wed, 12 Sep 2007 16:48:00 +0200	[thread overview]
Message-ID: <46E7FC20.8090003@bppiac.hu> (raw)
In-Reply-To: <slrnfeesv8.dn9.robert.sander@raman.epigenomics.epi>

Robert Sander wrote:
> On Wed, 12 Sep 2007 00:42:06 +0200,
>  Farkas Levente <lfarkas@bppiac.hu> wrote:
>> hi,
>> hi we've got a server with a lvm2 pv with a dozen of logvol in it. under
>> the lvm we'd like to create a raid1 array on 2 disk. unfortunately we
>> create raid0 under it. but the logvols contains a lots of important
>> data. we'd like to
>> - put 2 new disks into the system,
>> - create the raid1 array on it,
>> - put a new volgroup over the raid1,
> 
> Hi!
> 
> Do not create a new vg.
> Add the raid1 as a second pv to the existing vg.
> Use pvmove to move the logical volumes from one pv to the other.
> This is an online operatipn.

ok everything seems to working. after i move the logvols i remove the
old pv and try to boot the system. now the problem during the boot linux
can't find the volume group so can't find it's / since the / is on the
first logvol of the vg. this on centos-5.
the strange thing if i boot from centos rescue dvd it see the vg and
logvols too and i can chroot /mnt/sysimage into the new real system.
what can be the reason that if i boot the new system it can't find the
vg and it's logvols?

-- 
  Levente                               "Si vis pacem para bellum!"

  reply	other threads:[~2007-09-12 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 22:42 [linux-lvm] is it possible to move lvm2 logvols? Farkas Levente
2007-09-12  5:06 ` Robert Sander
2007-09-12 14:48   ` Farkas Levente [this message]
2007-09-12 15:51     ` Farkas Levente
2007-09-12 21:53     ` 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=46E7FC20.8090003@bppiac.hu \
    --to=lfarkas@bppiac.hu \
    --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.