From: Jon Bendtsen <jon+lvm@silicide.dk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] mounting reiserfs snaphost fails
Date: Fri Oct 4 08:41:06 2002 [thread overview]
Message-ID: <3D9D975D.DEDE70FE@silicide.dk> (raw)
In-Reply-To: 3D9D923B.5899DB6A@silicide.dk
Jon Bendtsen wrote:
>
> Xavier Montagutelli wrote:
> >
> > On Fri, 4 Oct 2002, Jon Bendtsen wrote:
> >
> > > "Heinz J . Mauelshagen" wrote:
[cut]
> Doing a cvs, i only found these 2 files (and others)
>
> linux-2.4.18+quota32-VFS-lock.patch
> linux-2.4.18-VFS-lock.patch
>
> nothing for 2.4.19 :/ (whats the difference between those 2 files?)
>
> I did a ./configure in the LVM dir, and a make in the PATCHES dir, and
> tried to
> apply that patch to a 2.4.19, and a 2.4.18, stock from Linus. They
> applied fine
> but they did not compile :/
> "drivers/md/mddev.o: In function `_proc_read_global':
> drivers/md/mddev.o(.text+0x6e1a): undefined reference to `vg'
> drivers/md/mddev.o(.text+0x702e): undefined reference to `lvm_memory'
> drivers/md/mddev.o(.text+0x71a1): undefined reference to `vg'
> make[1]: *** [vmlinux] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.4.18'
> make: *** [stamp-build] Error 2"
>
> So, right now i'm trying the same thing with only
> linux-2.4.18-VFS-lock.patch
> applied.
Okay, that "worked". It compiled, but i dont know if it can take
online snapshots of journaled filesystems (ext3). I'll try that.
JonB
prev parent reply other threads:[~2002-10-04 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 2:42 [linux-lvm] mounting reiserfs snaphost fails myciel
2002-08-29 3:52 ` Jon Bendtsen
2002-08-29 4:57 ` myciel
2002-08-29 6:18 ` Heinz J . Mauelshagen
2002-08-29 10:59 ` myciel
2002-10-04 3:09 ` Jon Bendtsen
2002-10-04 3:46 ` Jon Bendtsen
2002-10-04 3:58 ` Heinz J . Mauelshagen
2002-10-04 3:53 ` Xavier Montagutelli
2002-10-04 8:14 ` Jon Bendtsen
2002-10-04 8:41 ` Jon Bendtsen [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=3D9D975D.DEDE70FE@silicide.dk \
--to=jon+lvm@silicide.dk \
--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