Linux LVM users
 help / color / mirror / Atom feed
From: Dossy <dossy@panoptic.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 1.0.1 to LVM2 upgrade path
Date: Fri Feb  7 17:45:04 2003	[thread overview]
Message-ID: <20030207234501.GI22795@panoptic.com> (raw)
In-Reply-To: <20030207152340.A27442@sistina.com>

On 2003.02.07, Heinz J . Mauelshagen <mauelshagen@sistina.com> wrote:
> 
> If this is production, you want to upgrade to LVM 1.0.6 because LVM2
> is in beta still. [...]  The only major feature missing in LVM2 is
> 'pvmove' which we are working on right now.

Thanks.  This is exactly the kind of detail I was looking for.  

> It supports the LVM1 metadata (IOW: you can install it and use your
> volume groups created with LVM1). 

So, in order to upgrade to LVM2 there's no data conversion necessary, if
I understand you correctly.  That's very good news.

> You should give LVM2 a try on some test system please.

I might play around with it on my laptop (which runs Linux under VMware)
-- this way, if anything goes wrong, I just lose a virtual disk and not
real data.  :-)

(VMware is great for "experimenting" with filesystem code.  I haven't
actually experimented with LVM under VMware yet, though.  It'll be
interesting ...)

Thanks for your time, Heinz.  I appreciate it.

-- Dossy

-- 
Dossy Shiobara                       mail: dossy@panoptic.com 
Panoptic Computer Network             web: http://www.panoptic.com/ 
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)

  reply	other threads:[~2003-02-07 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 22:25 [linux-lvm] LVM 1.0.1 to LVM2 upgrade path Dossy
2003-02-07  8:27 ` Heinz J . Mauelshagen
2003-02-07 17:45   ` Dossy [this message]
2003-02-10  7:50     ` Heinz J . Mauelshagen

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=20030207234501.GI22795@panoptic.com \
    --to=dossy@panoptic.com \
    --cc=linux-lvm@sistina.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