From: Paul <set@pobox.com>
To: Patrick Finnegan <pat@purdueriots.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Moving from Linux 2.4.19 LVM to LVM2
Date: Wed, 13 Nov 2002 23:30:48 -0500 [thread overview]
Message-ID: <20021114043047.GU9928@squish.home.loc> (raw)
In-Reply-To: <Pine.LNX.4.44.0211132253340.11522-100000@ibm-ps850.purdueriots.com>
Patrick Finnegan <pat@purdueriots.com>, on Wed Nov 13, 2002 [11:05:37 PM] said:
> Is there an easy and plainless way to do this? Are the LVM2 tools
> backwards-compatible with the old LVM? I've got important partitions on
> LVM (/usr, /tmp, /var, /home) and I'd like to be able to switch back and
> forth between 2.4 and 2.5 kernels without needing to keep around separate
> copies of bootscripts and userland tools if possible.
>
> Thanks!
>
> Pat
Hi;
I have been playing with this. The userspace tools are
not backwards compatible. (2.4 tools didnt seem compatible
with 2.2 tools either-- Ive got 3 sets of them laying around)
Currently, LVM2 under 2.5 repeatedly will hit a BUG() and
oops for me. I also managed to destroy a test striped lv.
I wouldnt trust any important data to it yet.
(Jens Axboe has expressed a willingness to help with
the problem. Just a matter of time...)
You need a > 2.5.47 kernel (eg. a recent bk snapshot,
or eg. 2.5.47-ac2 or 2.5.45-mcp2) to even compile with
DM support if you want to play with this.
Paul
set@pobox.com
next prev parent reply other threads:[~2002-11-14 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 4:05 Moving from Linux 2.4.19 LVM to LVM2 Patrick Finnegan
2002-11-14 4:30 ` Paul [this message]
2002-11-14 8:20 ` Joe Thornber
2002-11-15 3:51 ` Patrick Finnegan
2002-11-15 9:49 ` Joe Thornber
2002-11-15 15:13 ` Patrick Finnegan
2002-11-15 15:39 ` Sean Neakums
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=20021114043047.GU9928@squish.home.loc \
--to=set@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pat@purdueriots.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