linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jesse Molina <jesse@opendreams.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using lvm1 vg's in lvm2 systems (RHEL4)
Date: Wed, 25 Oct 2006 16:18:47 -0700	[thread overview]
Message-ID: <20061025231847.GA17630@sorrows.opendreams.net> (raw)
In-Reply-To: <806e72ee0610250843k4e340b02s238835ce02626e9f@mail.gmail.com>


Thanks for indicating your solution.  I was having a very similar problem upgrading a Debian Unstable system a few months ago.  I still need to upgrade that system, so this might help me when that time comes around.



On Wed, Oct 25, 2006 at 12:43:56PM -0300, Fabricio Candido wrote:
>    Hi all.
> 
>       I've solved this problem downgrading the lvm version from RHEL4U2 to
>    RHEL4U1 included version.
> 
>    Thanks all.
> 
>    Fabricio
> 
>    On 10/17/06, Fabricio Candido <fabricio.candido@gmail.com> wrote:
> 
>      Alasdair,
> 
>        Thanks for your helping.
> 
>        I got these messages when I just execute vgdisplay, vgscan or pvscan:
> 
>        LV lv_oracle_data012: inconsistent LE count 252 != 1008
>        Internal error: LV segments corrupted in lv_oracle_data012.
>        LV lv_oracle_redo003: inconsistent LE count 4 != 16
>        Internal error: LV segments corrupted in lv_oracle_redo003.
>        LV lv_oracle_data020: inconsistent LE count 252 != 1008
>        Internal error: LV segments corrupted in lv_oracle_data020.
> 
>        I just imported these volumes in another RHEL3 server without
>      problems.
> 
>      Any ideas ?
> 
>      Regards,
>      Fabricio
>      On 10/17/06, Alasdair G Kergon <agk@redhat.com> wrote:
> 
>        On Tue, Oct 17, 2006 at 07:00:52PM -0300, Fabricio Candido wrote:
>        > Is it possible to my RHEL4 system use these lvm1 vgs without
>        converting it ?
>        > What is necessary ?
> 
>        Yes, provided you can manage without snapshots and pvmove.
>        [Alternatively, you can run vgconvert to update your metadata in-situ
>        to the
>        new lvm2 format.]
> 
>        Alasdair
>        --
>        agk@redhat.com
> 
>        _______________________________________________
>        linux-lvm mailing list
>        linux-lvm@redhat.com
>        https://www.redhat.com/mailman/listinfo/linux-lvm
>        read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 
# Jesse Molina
# Mail = jesse@opendreams.net
# Page = page-jesse@opendreams.net
# Cell = 1.602.323.7608
# Web  = http://www.opendreams.net/jesse/
 
 

      reply	other threads:[~2006-10-25 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 22:00 [linux-lvm] Using lvm1 vg's in lvm2 systems (RHEL4) Fabricio Candido
2006-10-17 22:39 ` Alasdair G Kergon
2006-10-17 23:21   ` Fabricio Candido
2006-10-25 15:43     ` Fabricio Candido
2006-10-25 23:18       ` Jesse Molina [this message]

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=20061025231847.GA17630@sorrows.opendreams.net \
    --to=jesse@opendreams.net \
    --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 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).