From: lewis@sistina.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Linux 2.4.0-test12-pre7 LVM .9 vs .8final
Date: Mon, 11 Dec 2000 08:32:58 -0600 [thread overview]
Message-ID: <20001211083258.A19073@sistina.com> (raw)
In-Reply-To: <3A3477D0.94BC1D88@twc.de>; from ulf@twc.de on Mon, Dec 11, 2000 at 07:44:32AM +0100
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
On Mon, Dec 11, 2000 at 07:44:32AM +0100, Ulf Bartelt wrote:
> Ricardo Muggli wrote:
> >
> > I have noticed that Linux 2.4.0-test12-pre7 still comes with .8final. Is
> > there a plan to have .9 incorporated at some future time into the stock
> > 2.4 kernels? Will this happen before 2.4 comes out?
> >
> > Also is there a transition path between .8final and .9? (short of save
> > everything to tape and restore?)
>
> I was wondering ´bout the same question yesterday...
>
> A set of lvm tools for multiple versions of the io protocol could help a
> lot...
>
> Sure this can be faked using links, wrappers etc...
I dunno if this is what you guys are asking for or not, but...as I've been
testing LVM-0.8.1. and LVM-0.9, I've used the same VG and LV. For the
transition, all I need to do is do a 'vgchange -ay' to reactivate the volume
group using the other version of LVM. I haven't done anything too complicated
with this, but for my very basic testing, this has worked fine. So basically
the transition path (If I am correct) between 0.8final and 0.9 is:
1) patch a kernel with the 0.9 patches
2) compile lvm-0.9
3) install the new kernel and lvm-0.9
4) run lilo
5) reboot
Of course, if you are using LVM as your root filesystem, this is a bit
trickier I guess...you probably have to make a lvm-0.9 bootdisk and use that
to activate the VG...
I am definitely not an expert on this though, so take it with a grain of
salt...
Can anyone else comment on this?
Regards,
--
AJ Lewis
Sistina Software Inc. Voice: 612-379-3951
1313 5th St SE, Suite 111 Fax: 612-379-3952
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Over and over I find being redundant is key to success
in the art of redundancy - Jay Armstrong
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-12-11 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 16:47 [linux-lvm] Linux 2.4.0-test12-pre7 LVM .9 vs .8final Ricardo Muggli
2000-12-11 6:44 ` Ulf Bartelt
2000-12-11 14:32 ` lewis [this message]
2000-12-12 9:06 ` Ulf Bartelt
2000-12-12 7:48 ` Luca Berra
2000-12-12 23:07 ` lewis
2000-12-13 7:36 ` Luca Berra
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=20001211083258.A19073@sistina.com \
--to=lewis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox