From: Vegard Engen <vegard@engen.priv.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and Kernel 2.4.3
Date: Wed, 18 Apr 2001 17:08:58 +0200 [thread overview]
Message-ID: <20010418170858.I31343@engen.priv.no> (raw)
In-Reply-To: <3ADDA60F.8F8F65DE@isoco.com>; from jferruz@isoco.com on Wed, Apr 18, 2001 at 04:34:55PM +0200
On Wed, Apr 18, 2001 at 04:34:55PM +0200, Javier Ferruz wrote:
>
> I would like install LVM with kernel version
> 2.4.3. I downloaded version 0.9.1beta7.
>
> The variables in PATCHES/Makefile are:
>
>
> KERNEL_DIR=/usr/src/linux
> LVM_VERSION=0.9.1_beta7
> KERNEL_VERSION=2.4.3
>
> The file PATCHES/README said "type 'make',
> a file of the form
> lvm-<LVM_VERSION>-<KERNEL_VERSION>.patch
> should be built, but I haven't any file
> for version 2.4.3.
>
> Can I use LVM with version 2.4.3 or I have to
> install 2.4.2?
I'm using LVM with version 2.4.3 and 0.9.1beta6 (out of convenience, there
was a debian package of it). I did the above. It worked, the patch applied
flawlessly. I *did* however get some problems, but it seems to be strictly
LVM snapshot-related, and did not cause any errors on the real volume. I sent
a detailed report to this list yesterday. I will, however, not trust LVM
snapshot yet for backup. And I have a full backup of the system in case
somehing *should* go wrong, although I have no reason to think so.
In fact, I've done a lot of LVM-manipulation these last few days, none of
them really failed, except for LVM snapshot. I have not tried things like
pvmove of a mounted system, though, but I have done lvextend and extended
filesystems on mounted filesystems.
- Vegard
prev parent reply other threads:[~2001-04-18 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 14:34 [linux-lvm] LVM and Kernel 2.4.3 Javier Ferruz
2001-04-18 15:08 ` Vegard Engen [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=20010418170858.I31343@engen.priv.no \
--to=vegard@engen.priv.no \
--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;
as well as URLs for NNTP newsgroup(s).