All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 1.0.1 to LVM2 upgrade path
Date: Mon Feb 10 07:50:02 2003	[thread overview]
Message-ID: <20030210144647.B5997@sistina.com> (raw)
In-Reply-To: <20030207234501.GI22795@panoptic.com>; from dossy@panoptic.com on Fri, Feb 07, 2003 at 06:45:01PM -0500

On Fri, Feb 07, 2003 at 06:45:01PM -0500, Dossy wrote:
> 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.

No, you can stick with the LVM1 metadata w/o ayn conversion.
If you want to use the enhanced LVM2 metadata format you need to convert
thought (see vgconvert).  The LVM2 metadata format will give you
atomic metadata updates for better system resilience.

> 
> > 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.  :-)

Yep, that's a way.

> 
> (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)
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2003-02-10  7:50 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
2003-02-10  7:50     ` Heinz J . Mauelshagen [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=20030210144647.B5997@sistina.com \
    --to=mauelshagen@sistina.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 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.