On Fri, Feb 4, 2011 at 2:20 AM, Joel Becker <jlbec@xxxxxxxxxxxx> wrote: > 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. > Cool. I'd love to see a draft (if you already posted it I missed it). I wonder how one deals with different fs with different snapshot capabilities, i.e. file level vs. sub/volume level. which one is the case for ocfs2? > Joel > > -- > > "Sometimes one pays most for the things one gets for nothing." > - Albert Einstein > > http://www.jlbec.org/ > jlbec@xxxxxxxxxxxx > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
