From: "Fabricio Candido" <fabricio.candido@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using lvm1 vg's in lvm2 systems (RHEL4)
Date: Tue, 17 Oct 2006 20:21:28 -0300 [thread overview]
Message-ID: <806e72ee0610171621p1cb6e9d2r795002ce70293177@mail.gmail.com> (raw)
In-Reply-To: <20061017223949.GP17654@agk.surrey.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
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/
>
[-- Attachment #2: Type: text/html, Size: 2795 bytes --]
next prev parent reply other threads:[~2006-10-17 23:21 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 [this message]
2006-10-25 15:43 ` Fabricio Candido
2006-10-25 23:18 ` Jesse Molina
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=806e72ee0610171621p1cb6e9d2r795002ce70293177@mail.gmail.com \
--to=fabricio.candido@gmail.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 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).