From: "Wolfgang Weisselberg" <uzx87lvfmukwc001@sneakemail.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 1.0.7, kernel 2.4.21 and snapshots over ext3 filesystem
Date: Fri Jul 4 15:59:01 2003 [thread overview]
Message-ID: <12023-88653@sneakemail.com> (raw)
In-Reply-To: <BC28A9E979C56C44BCBC2DED313A4470017E83E8@bond.ncl.ac.uk>
C R Ritson C.R.Ritson-at-newcastle.ac.uk |LVM Mailinglist linux-lvm/Allow| wrote 45 lines:
> > My bet is that you first patched the kernel for VFS-lock and
> > *then* patched the kernel for LVM. This undoes (parts of)
> > the VFS-lock. The reason is as follows:
> That is strange - my exprience with kernel 2.4.20 and LVM 1.0.7 was as
> follows:
> Attempting to apply the VFS-lock patch AFTER the LVM generated patch
> gives me an un-compilable tree with with unresolved reverences to
> fsync_dev_lockfs and unlockfs.
I have compiled quite a few kernels exactly after my cheatsheet
(from at least 2.4.21-rc1 up to my currently running 2.4.21-lvm)
and it works. At times I may have to hand-patch because of
trivial changes to get the VFS-lock patch in, but ... that's it.
> On one test machine I am running a 2.4.20 kernel in which the VFS-lock
> patch was applied BEFORE the LVM patch. Here, I am taking a snapshot at
> Would Heinz care to comment on these two apparently conflicting results?
It MIGHT be that LVM 1.0.7 is in sync (or at least not damaging)
to the VFS-lock patch for 2.4.20. I *have* had problems in the
past (I tried VFS-lock and the LVM and it failed), but I cannot
vouch that they are there for kernel 2.4.20/LVM 1.0.7.
-Wolfgang
next prev parent reply other threads:[~2003-07-04 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 11:14 [linux-lvm] LVM 1.0.7, kernel 2.4.21 and snapshots over ext3 filesystem C R Ritson
2003-07-04 15:59 ` Wolfgang Weisselberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-01 12:09 Alberto Picon Couselo
2003-07-01 16:17 ` Wolfgang Weisselberg
2003-07-02 8:05 ` Alberto Picon Couselo
2003-07-04 15:31 ` Wolfgang Weisselberg
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=12023-88653@sneakemail.com \
--to=uzx87lvfmukwc001@sneakemail.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.