archive mirror
 help / color / mirror / Atom feed
From: Tupshin Harper <>
To: Matthias Andree <>
Cc: Linux-Kernel mailing list <>
Subject: Re: LVM2 user space, device mapper, Linux 2.4/2.6 dual boot no-go.
Date: Wed, 16 Jul 2003 15:33:36 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Matthias Andree wrote:

>here's the situation:
>I want to test drive 2.6, have 2.4.22-pre3-ac1 with LVM1, Device Mapper
>and XFS. I tried LVM2 user space on 2.4.22, it complained about ioctl
>mismatch (wants 4.x.y, gets 1.m.n). Do I need to disable LVM1?
>On 2.6, lvm lvmdiskscan works, but lvm vgscan stuffs my screen with
>"modprobe junk.", so I reverted to 2.4-with-LVM1-user-space for now.
>Has anyone had success with running the same user-space LVM2 stuff on
>2.4 and 2.6? Which versions of device-mapper and LVM2 do you use for
>that purpose? What are the magic switches in Linux-2.4.22-preX-acY?
>Help appreciated.
I'm running LVM2 on 2.4.21-ac4, and that works just fine for me (debian 
sid, with the lvm2 package from the distribution). While 2.5/6 is still 
too unstable for me to use for long (for unrelated reasons) , it does 
boot up correctly and function with 25 lvm2 partitions on four different 
lvm groups. I would get it working correctly on your 2.4 kernel first. 
There were not magic incantations for me...what distribution are you 
using, and where are you getting LVM2 from?


      parent reply	other threads:[~2003-07-16 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  9:53 LVM2 user space, device mapper, Linux 2.4/2.6 dual boot no-go Matthias Andree
2003-07-16 14:17 ` Joe Thornber
2003-07-16 22:33 ` Tupshin Harper [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).