public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Moving from Linux 2.4.19 LVM to LVM2
Date: Fri, 15 Nov 2002 15:39:24 +0000	[thread overview]
Message-ID: <6uheei6dw3.fsf@zork.zork.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0211151012470.14891-100000@ibm-ps850.purdueriots.com> (Patrick Finnegan's message of "Fri, 15 Nov 2002 10:13:19 -0500 (EST)")

commence  Patrick Finnegan quotation:

> On Fri, 15 Nov 2002, Joe Thornber wrote:
>
>> On Thu, Nov 14, 2002 at 10:51:48PM -0500, Patrick Finnegan wrote:
>> > On Thu, 14 Nov 2002, Joe Thornber wrote:
>> >
>> > > On Wed, Nov 13, 2002 at 11:05:37PM -0500, Patrick Finnegan wrote:
>> > > > Is there an easy and plainless way to do this?  Are the LVM2 tools
>> > > > backwards-compatible with the old LVM?
>> > >
>> > > Yes
>> >
>> > Actually, the answer is aparently "No."  LVM2's tools don't work with a
>> > 2.4.x kernel.
>>
>> Had you applied the device-mapper patches for 2.4 ?
>
> Umm, no.  If I had, then that wouldn't be 2.4's native LVM.

The LVM1 tools require the lvm module.  The LVM2 tools require the
device-mapper module (and therfore, for 2.4, a patch).  LVM2 is
backward-compatible with LVM1 in the sense that LVM2 can use
LVM1-created volume groups.

I've been running LVM2 (I used to use LVM1) on my laptop for the past
few weeks (2.4.19, also patched with rmap14b), and it's been
completely trouble-free.

-- 
 /                          |
[|] Sean Neakums            |  Questions are a burden to others;
[|] <sneakums@zork.net>     |      answers a prison for oneself.
 \                          |

      reply	other threads:[~2002-11-15 15:32 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
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 [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=6uheei6dw3.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --cc=linux-kernel@vger.kernel.org \
    /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