All of lore.kernel.org
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Patch for Kernel 2.2.16
Date: Fri, 19 Jan 2001 10:17:57 -0600	[thread overview]
Message-ID: <20010119101757.K23203@sistina.com> (raw)
In-Reply-To: <615A249B783CD41192F400D0B747AC8601A001EB@hesse.bbn.hp.com>; from holger_zecha@hp.com on Fri, Jan 19, 2001 at 04:19:54PM +0100

[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]

On Fri, Jan 19, 2001 at 04:19:54PM +0100, ZECHA,HOLGER (HP-Germany,ex1) wrote:
> is there a lvm patch for kernel 2.2.16 available ?

By following the instructions in the PATCHES/README file for 0.9.1 Beta2, I
was able to generate a patch that appears to work for 2.2.16.  I copied the
fragments-2.2.18 file to fragments-2.2.16 and ran 'make' in the PATCHES
directory.  This created a file called lvm-0.9.1_beta2-2.2.16.patch.

I grabbed the 2.2.16 rawio patch from the 0.8.1 release of LVM.  (You can
get this from the LVM ftp site at
ftp://ftp.sistina.com/LVM/0.8.1/PATCHES/linux-2.2.16-rawio.patch)  I applied
this rawio patch and the generated lvm patch to the clean 2.2.16 kernel,
configured, and built the kernel.  After installing the kernel and rebooting
the machine, I was able to see the volume group i had created with a 2.2.18
kernel and LVM 0.9.1 Beta2.  I mounted a logical volume from the volume
group, and was able to use it.  

That is the extent of the testing I have done, so if you are worried about
your data, don't do this!  Or at least backup your data before trying it.
Good luck.

-- 
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
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
Students nowadays, complaining they only get 5MBs of disk space!
In my day we were lucky if we had one file, and that was /dev/null.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-01-19 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-19 15:19 [linux-lvm] Patch for Kernel 2.2.16 ZECHA,HOLGER (HP-Germany,ex1)
2001-01-19 16:17 ` AJ Lewis [this message]
2001-01-19 16:49   ` AJ Lewis
2001-01-19 17:22     ` Joe Thornber
2001-01-19 19:51       ` AJ Lewis
2001-01-20 17:51         ` Joe Thornber
2001-01-19 18:17     ` Heinz J. Mauelshagen
2001-01-19 21:04       ` Chris Mason
2001-01-19 16:24 ` Joe Thornber

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=20010119101757.K23203@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.