From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM2 and Kernel 2.5.xx
Date: Wed Oct 9 06:09:02 2002 [thread overview]
Message-ID: <20021009130737.C23965@sistina.com> (raw)
In-Reply-To: <20021007143359.GB1978@glorybox.de>; from lists@glorybox.de on Mon, Oct 07, 2002 at 04:33:59PM +0200
On Mon, Oct 07, 2002 at 04:33:59PM +0200, Kai Weber wrote:
> + Heinz J . Mauelshagen <mauelshagen@sistina.com>:
>
> > the device-mapper code to Linus ASAP. This is supposed to be the
> > replacement for the LVM1 driver in 2.5 together with the LVM2 tools
> > (which are LVM1 compatible).
>
> How will the migration from LVM1 to LVM2 work? Would LVM1 volumes
> be easily convertible into LVM2 without data loss?
LVM2 is completely metadata format compatible with LVM1.
IOW: it supports the LVM1 metadata read-write.
The upgrade is a matter of installing the LVM2 and device-mapper
software (properly ;-) and running "vgscan ; vgchange -ay".
>
> Kai
>
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-10-09 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 1:45 [linux-lvm] LVM2 and Kernel 2.5.xx david
2002-10-07 3:38 ` Joe Thornber
2002-10-07 3:51 ` Heinz J . Mauelshagen
2002-10-07 9:47 ` Kai Weber
2002-10-09 6:09 ` 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=20021009130737.C23965@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.