From: Greg Freemyer <freemyer-ml@NorcrossGroup.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM Snapshots for remote archiving.
Date: Thu Jan 29 11:52:02 2004 [thread overview]
Message-ID: <1075394278.25365.93.camel@david.internal.NorcrossGroup.com> (raw)
In-Reply-To: <401807B2.6060900@gene.concordia.ca>
On Wed, 2004-01-28 at 14:04, Chris Beck wrote:
> >I don't think that is a trivial issue, and I think the code would have
> >to implemented in the kernel.
> >
> >
> Why the kernel? ... surely reading the flag tables could be done in user
> space? I think you have the necessary logic spot on.
I don't think the COW flag table is accessible from userspace, but I
could be wrong.
FYI: I am a LVM user, not a developer.
>
> >New code would also have to be developed to apply the above blocks.
> >
> >
> Hmmm. I can mess around in perl and java as well as the next guy, but
> my c-fu is weak, very weak. How much would it cost to sponsor someone
> to do this do you think?
I don't have any idea. If your serious, I would recommend doing it with
LVM 2 (requires DM in the kernel), since DM is part of 2.6.x vanilla and
2.6.x will not likely ever support LVM 1.x.
In that case, I would post on the dm-devel list. There seem to be a few
non-Sistina people that are very knowledgable and post regularily.
http://lists.sistina.com/mailman/listinfo/dm-devel
FYI: Since Sistina is in the process of being bought by Redhat, I doubt
they would consider a new project (or sub-project) right now.
HTH
Greg
--
Greg Freemyer
prev parent reply other threads:[~2004-01-29 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 18:05 [linux-lvm] LVM Snapshots for remote archiving Chris Beck
2004-01-27 18:46 ` Greg Freemyer
2004-01-28 11:44 ` Chris Beck
2004-01-28 12:33 ` Greg Freemyer
2004-01-28 14:06 ` Chris Beck
2004-01-29 11:52 ` Greg Freemyer [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=1075394278.25365.93.camel@david.internal.NorcrossGroup.com \
--to=freemyer-ml@norcrossgroup.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.