From: Andreas Dilger <adilger@turbolabs.com>
To: Adrian Head <ahead@bigpond.net.au>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] summary of what I need to do to mount snapshot on XFS
Date: Tue Jan 15 11:48:02 2002 [thread overview]
Message-ID: <20020115104724.B11251@lynx.adilger.int> (raw)
In-Reply-To: <E16QVD9-0003HS-00@hermes.sistina.com>; from ahead@bigpond.net.au on Wed, Jan 16, 2002 at 01:09:16AM +1000
On Jan 16, 2002 01:09 +1000, Adrian Head wrote:
> On Wed, 16 Jan 2002 00:16, Heinz J . Mauelshagen wrote:
> > > The lvm.c change you talk about I assume is the LVM_VFS_ENHANCEMENT
> > > change? For some reason when adding the lvm-1.0.1 upgrade patch this
> > > disappears from lvm.c I have been able to get this to compile with the
> > > change but I have forgoten what I did.
> > >
> > > This is one question I would like answered by the LVM gurus: should
> > > #define LVM_VFS_ENHANCEMENT still be there after upgrading to lvm-1.0.1?
> >
> > Yes.
>
> I have found that using the generated lvm-1.0.1 upgrade patch that the
> #define LVM_VFS_ENHANCEMENT gets removed. If all I do is add it back in
> manually - do I need to worry about other areas of the code that also need
> touch-ups? How would I tell?
Well, when you generate a new LVM patch it will just do a "diff" between
the lvm.c file in the LVM/kernel directory and the linux/md/lvm.c file.
If the VFS-lock patch is applied to the kernel sources and not the
LVM/kernel sources, it will be removed by the diff, meaning you will
need to apply the VFS-lock patch to the kernel again.
If you find you are doing a lot of patching, you could apply the VFS-lock
patch to the LVM/kernel/lvm.c file, and then subsequent patches that you
create will not have this part removed.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-15 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 9:22 [linux-lvm] summary of what I need to do to mount snapshot on XFS Jeremy Hansen
2002-01-09 6:07 ` Adrian Head
2002-01-09 7:04 ` Patrick Caulfield
2002-01-09 14:23 ` Jeremy Hansen
2002-01-09 17:39 ` Adrian Head
2002-01-15 8:19 ` Heinz J . Mauelshagen
2002-01-15 9:10 ` Adrian Head
2002-01-15 11:48 ` Andreas Dilger [this message]
2002-01-09 14:34 ` Jeremy Hansen
2002-01-10 2:40 ` Anselm Kruis
2002-01-09 14:51 ` Jeremy Hansen
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=20020115104724.B11251@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=ahead@bigpond.net.au \
--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).