From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshot of Reiserfs
Date: Wed, 21 Feb 2001 14:11:20 +0000 [thread overview]
Message-ID: <20010221141119.I568@tykepenguin.com> (raw)
In-Reply-To: <14995.51952.832793.443201@nv.winux.com>; from lvm@winux.com on Wed, Feb 21, 2001 at 09:04:32AM -0500
On Wed, Feb 21, 2001 at 09:04:32AM -0500, lvm@winux.com wrote:
> Patrick Caulfield writes:
> > From: Patrick Caulfield <caulfield@sistina.com>
> > Sender: linux-lvm-admin@sistina.com
> > To: linux-lvm@sistina.com
> > Subject: Re: [linux-lvm] snapshot of Reiserfs
> > Date: Wed, 21 Feb 2001 08:59:59 +0000
> >
> > On Tue, Feb 20, 2001 at 11:19:51PM -0500, lvm@winux.com wrote:
> > > Heinz J. Mauelshagen writes:
> > > > ... Linux Logical Volume Manager 0.9.1 Beta 5 is available now ...
> > > > ...
> > > > Please help us to stabilize for 0.9.1 ASAP and test is as much as possible!
> > >
> > > I am using LVM 0.9.1 beta 5 on Linux 2.4.1 with Reiserfs.
> > > I have applied both of the following patches:
> > >
> > > 0.9.1_beta5/PATCHES/lvm-0.9.1_beta5-2.4.1.patch
> > > 0.9.1_beta5/PATCHES/linux-2.4.1-VFS-lock.patch
> > >
> > > Snapshots created when the filesystem is active cannot be mounted.
> > > If I `umount' the filesystem before creating the snapshot, all is well.
> >
> > Did you remember to uncomment LVM_VFS_ENHANCEMENT in lvm.c ?
> >
> > patrick
>
> Bingo! That was the problem! Many thanks!
>
> Shouldn't that change be included in the VFS-lock patch?
It complicates the order of applying them but it's a fair point.
> In fact, why are these separate patches? Shouldn't they
> eventually be "the standard" and find their way into the
> stock kernel? It's arguably the correct behavior.
That is the intension. The patch is Chris Mason's and I beleive
he is trying to get it into the kernel. Heinz emailed him about
it recently, I don't know if he has had any reply yet.
Patrick
next prev parent reply other threads:[~2001-02-21 14:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 22:49 [linux-lvm] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com Heinz J. Mauelshagen
2001-02-20 22:42 ` [lvm-devel] " Andrea Arcangeli
2001-02-21 0:31 ` Andreas Dilger
2001-02-21 1:12 ` Andrea Arcangeli
2001-02-21 3:49 ` Richard Gooch
2001-02-21 17:00 ` Andrea Arcangeli
2001-02-21 17:03 ` Richard Gooch
2001-02-21 17:18 ` Christoph Hellwig
2001-02-22 4:12 ` Peter Samuelson
2001-02-22 9:46 ` Christoph Hellwig
2001-02-22 10:52 ` Peter Samuelson
2001-02-22 11:53 ` Christoph Hellwig
2001-02-21 4:19 ` [linux-lvm] snapshot of Reiserfs lvm, lvm
2001-02-21 8:59 ` Patrick Caulfield
2001-02-21 14:04 ` lvm
2001-02-21 14:11 ` Patrick Caulfield [this message]
2001-02-21 15:34 ` Chris Mason
2001-02-21 16:05 ` lvm
2001-02-21 16:12 ` Patrick Caulfield
2001-02-21 16:44 ` Andreas Dilger
2001-02-21 17:07 ` Chris Mason
2001-02-21 18:55 ` Andreas Dilger
2001-02-21 19:17 ` Chris Mason
2001-02-21 23:23 ` Andreas Dilger
2001-02-22 17:12 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 6:31 [linux-lvm] Snapshot of ReiserFS Dietmar Stein
2001-02-19 16:11 [linux-lvm] snapshot of Reiserfs lvm
2001-02-19 16:12 ` Joe Thornber
2001-02-19 17:04 ` Christoph Hellwig
2001-02-19 16:59 ` Joe Thornber
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=20010221141119.I568@tykepenguin.com \
--to=caulfield@sistina.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.