From: Joel Becker <jlbec@evilplan.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: lsf-pc@lists.linuxfoundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: [LSF/FS TOPIC] Ext4 snapshots status update
Date: Thu, 3 Feb 2011 16:20:44 -0800 [thread overview]
Message-ID: <20110204002043.GA15658@noexit> (raw)
In-Reply-To: <AANLkTink6o249JivXiETT6JnANNcikNqGGfr8+McDQsM@mail.gmail.com>
On Fri, Feb 04, 2011 at 12:33:39AM +0200, Amir Goldstein wrote:
> I have been working on porting Next3 snapshots to Ext4
> with a group of 4 CS students.
>
> This is where it all happens:
> https://github.com/amir73il/ext4-snapshots
>
> Ext4 snapshots prototype is already working!
> Would you like to see a demo?
>
> I would like to present the progress of our work
> and discuss the remaining issues and how they should be best addressed.
>
> Additionally, I would like to discuss the need for a unified snapshots API that
> would serve both Ext4 and Btrfs.
> This could be useful for someone that wants to implement a generic
> snapshots management system.
ocfs2 definitely wants to be a part of that discussion, as we
already do snapshots and thin clones. ocfs2 snapshots are actually just
thin clones marked readonly. They can be placed anywhere in the
filesystem and are first-class inodes. They do not live in a hidden
space like Next3 snapshots seem to.
I've already got a design for a front-end snapshot program that
implements a policy on top this generic behavior. This design would
cover both first-class and hidden style snapshots, because it assume
snapshots are in a distinct namespace. I haven't gotten around to
implementing it yet, but btrfs and other snapshottable filesystems were
part of the design goal.
Joel
--
"Sometimes one pays most for the things one gets for nothing."
- Albert Einstein
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-02-04 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 22:33 [LSF/FS TOPIC] Ext4 snapshots status update Amir Goldstein
2011-02-04 0:20 ` Joel Becker [this message]
2011-02-04 5:52 ` Amir Goldstein
2011-03-23 20:19 ` Amir Goldstein
2011-03-30 0:34 ` Joel Becker
2011-03-30 4:16 ` Amir Goldstein
2011-03-30 5:52 ` Tao Ma
2011-03-30 6:05 ` Amir Goldstein
2011-03-30 10:33 ` Joel Becker
2011-03-30 10:46 ` Amir Goldstein
2011-03-30 11:50 ` Chris Mason
2011-03-30 12:08 ` Amir Goldstein
2011-04-01 0:10 ` [Lsf-pc] " Trond Myklebust
2011-04-01 3:58 ` Amir Goldstein
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=20110204002043.GA15658@noexit \
--to=jlbec@evilplan.org \
--cc=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).