From: Erik Hensema <erik@hensema.net>
To: linux-kernel@vger.kernel.org
Subject: Re: LVM migration for 2.4->2.6, fallback path?
Date: Sun, 11 Jan 2004 23:05:24 +0000 (UTC) [thread overview]
Message-ID: <slrnc03llk.fvn.erik@dexter.hensema.net> (raw)
In-Reply-To: <20040111222223.GA9884@merlin.emma.line.org>
Matthias Andree (matthias.andree@gmx.de) wrote:
> Hi,
>
> I understand that the following three combinations work (assuming
> 2.4.24/2.6.1):
>
> Userspace Kernelspace
> ------------------------------------------
> LVM1 2.4 LVM
> LVM2 2.4 + devmapper patch
> LVM2 2.6
>
> But will LVM2 + 2.4 LVM work? LVM1 + 2.6 will not.
Just don't resize your volumes in 2.6, and you'll be fine.
Resizing causes 'vendor lock in' though ;-)
> I presume neither works, but if there is a way, I'd like to know to save
> myself some work.
>
> Oh, and while I'm at it, what good is the "old ioctl" switch in kernel
> space? I am currently trying without and it works fine with a current
> LVM2 version (which is presumably how things are meant to be).
Just use the new ioctl, the old is just for compatibility with an
old lvm2 userspace. Clearly you don't have that.
--
Erik Hensema <erik@hensema.net>
prev parent reply other threads:[~2004-01-11 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 22:22 Matthias Andree
2004-01-11 23:05 ` Erik Hensema [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=slrnc03llk.fvn.erik@dexter.hensema.net \
--to=erik@hensema.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
all inboxes | Powered by JetHome®