From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] can't snap a mounted (reiserfs|ext3) with kernel 2.2.x
Date: Sat Aug 24 14:20:01 2002 [thread overview]
Message-ID: <1030216872.17780.89.camel@tiny> (raw)
In-Reply-To: <20020824090719.GA5327@tykepenguin.com>
On Sat, 2002-08-24 at 05:07, Patrick Caulfield wrote:
> On Fri, Aug 23, 2002 at 11:56:45AM +0200, Thierry VOYAT wrote:
> > I need to unmount the lvm partition before i can realize a valid
> > snapshot of a journalized fs (reiserfs or ext)
> > All works fine with ext2 :
> >
> > I known there was a patch for kernel 2.4.x for VFS-lock but nothing for
> > kenel 2.2.x series.
> >
> > I can't upgrade to kernel 2.4. What can i do ?
>
> I don't think there is such a thing as the VFS lock patch for 2.2 (unless Chris
> Mason knows otherwise!).
>
> In which case, Im afraid, you're stuck.
We do have patch in the 2.2.x suse kernel to add the lockfs calls to the
kernel, but not a reiserfs patch to use them. Anyone know if 2.2.x ext3
provides a lockfs call?
-chris
prev parent reply other threads:[~2002-08-24 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 5:01 [linux-lvm] can't snap a mounted (reiserfs|ext3) with kernel 2.2.x Thierry VOYAT
2002-08-24 4:08 ` Patrick Caulfield
2002-08-24 14:20 ` Chris Mason [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=1030216872.17780.89.camel@tiny \
--to=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox