From: Tracy R Reed <treed@ultraviolet.org>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Snapshots with 2.4.1?
Date: Wed, 7 Feb 2001 14:25:10 -0800 [thread overview]
Message-ID: <20010207142510.D16262@ultraviolet.org> (raw)
In-Reply-To: <20010202165642.A1955@66bassett.freeserve.co.uk>; from joe@66bassett.freeserve.co.uk on Fri, Feb 02, 2001 at 04:56:42PM +0000
On Fri, Feb 02, 2001 at 04:56:42PM +0000, Joe Thornber wrote:
> 2.4.1 hadn't been released when we made the beta3 tarball. If you
> want to make a beta3 patch for the kernel create an empty file call
> PATCHES/fragments-2.4.1 (2.4.1 needs no extra fragments) then run
> PATCHES/make. That should remove all the conflicts.
I need to get snapshots working with 2.4.1. I've tried using just the
straight LVM that comes with the kernel and I have tried applying the
patches as described above. I either case, when I uncomment:
#define LVM_VFS_ENHANCEMENT
in drivers/md/lvm.c to enable the hooks for snapshots the compile fails:
drivers/md/mddev.o: In function `lvm_do_lv_create':
drivers/md/mddev.o(.text+0x11bdb): undefined reference to `fsync_dev_lockfs'
drivers/md/mddev.o(.text+0x11c90): undefined reference to `unlockfs'
Can someone point out what else I am missing?
--
Tracy Reed http://www.ultraviolet.org
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer
next prev parent reply other threads:[~2001-02-07 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 10:15 [linux-lvm] with 2.4.1, should I use beta2 or beta3 lvm-tools? Håkan Jettingstad
2001-02-02 10:30 ` Joe Thornber
2001-02-02 13:53 ` Rik van Riel
2001-02-02 15:54 ` Joe Thornber
2001-02-02 16:35 ` Rik van Riel
2001-02-02 16:58 ` Joe Thornber
2001-02-02 17:33 ` Rik van Riel
2001-02-02 16:25 ` Gregory McLean
2001-02-02 16:56 ` Joe Thornber
2001-02-07 22:25 ` Tracy R Reed [this message]
2001-02-07 22:32 ` [linux-lvm] Snapshots with 2.4.1? Chris Mason
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=20010207142510.D16262@ultraviolet.org \
--to=treed@ultraviolet.org \
--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.