From: Patrick Caulfield <pcaulfie@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgimport/vgexport commands when logically moving disks between systems
Date: Thu, 14 Dec 2006 13:49:29 +0000 [thread overview]
Message-ID: <45815669.5000107@redhat.com> (raw)
In-Reply-To: <298476.26347.qm@web51103.mail.yahoo.com>
Dave wrote:
> Hi Patrick,
>
> Thanks for clarifying the status of LVM1 (ie. *not* a clustering tool). That's
> somewhat surprising since it does include an LVM script in the resource.d directory.
> In any case, we're not in a huge rush to upgrade to LVM2 unless it really is
> necessary, as these are RH AS3 boxes running the 2.4.21-47.ELsmp kernel, and the
> docs I've read suggest LVM2 really needs/wants to run under a 2.6.x kernel.
Yes. there are device-mapper patches for 2.4 but it's really recommended to run 2.6.
> If direct-io to metadata could be set as an option under LVM1, assuming that isn't
> the default, that would be helpful. But, it sounds like no one really wants to
> support LVM1 anymore?!
That's true. lvm1 is in maintenance mode for RHEL3.
> Assuming we want to go forward with an upgrade to LVM2 on the current systems, how
> involved is that procedure? Do we risk losing all our data?
No. lvm2 can read and write lvm1 metadata. you can upgrade it to lvm2 format metadata with a single command (vgconvert)
--
patrick
next prev parent reply other threads:[~2006-12-14 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 9:38 [linux-lvm] vgimport/vgexport commands when logically moving disks between systems Dave
2006-12-05 10:28 ` Patrick Caulfield
2006-12-06 15:12 ` Dave
2006-12-06 15:54 ` Patrick Caulfield
2006-12-14 13:37 ` Dave
2006-12-14 13:49 ` Patrick Caulfield [this message]
2006-12-14 15:09 ` Alasdair G Kergon
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=45815669.5000107@redhat.com \
--to=pcaulfie@redhat.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).