From: Matt Zimmerman <mdz@debian.org>
To: "'user-mode-linux-devel@lists.sourceforge.net'"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Separate COW patch.
Date: Sat, 27 Sep 2003 21:44:32 -0400 [thread overview]
Message-ID: <20030928014432.GP9124@alcor.net> (raw)
In-Reply-To: <2D4B6CD74137D4119A1100104BC6BCBF0BC585FC@dubntex006.qwest.net>
On Fri, Sep 26, 2003 at 06:45:26PM -0400, Montgomery, Kendal L wrote:
> I was wondering if there was anyone who is trying to use the COW
> filesystem in a normal linux kernel? Is this possible, or is it tied
> exclusively to the rest of the UML patch? How difficult would it be to
> make a COW only patch? I have a certain project that I'm working on that
> the COW filesystem (or really, any other "union" filesystem, but I can't
> find any that are actively developed or fully cooked) would be perfect
> for. I have a read-only filesystem that, occasionally needs to
> temoroarily have some changed made to it, but then the need to be undone.
> I've looked into various ways of doing this from "snapshotting," to
> user-controlled transactions on a journalling filesystem (no such thing
> seems to exist for ext3 or reiserfs) where I could explicitly begin a
> transaction, then roll back the transaction when I'm done (kinda like a
> database txn), etc. The COW filesystem seems like it would be a perfect
> fit, but before I go trying to merge things into a non-UML kernel on my
> own I just want to see if anyone else has already done this or not. Is
> anyone else even interested in such a
You want the snapshot feature in device-mapper, with lvm2 or evms. It does
exactly what you've described, with any filesystem.
--
- mdz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2003-09-28 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 22:45 [uml-devel] Separate COW patch Montgomery, Kendal L
2003-09-26 23:14 ` Goetz Bock
2003-09-27 0:02 ` Jeff Dike
2003-09-27 22:56 ` Michael Richardson
2003-09-28 0:00 ` Paul Sladen
2003-09-28 1:44 ` Matt Zimmerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 16:53 Montgomery, Kendal L
2003-10-06 21:23 ` Jeff Dike
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=20030928014432.GP9124@alcor.net \
--to=mdz@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.