LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 07-04-2009, 07:22 PM   #1
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 115Reputation: 115
looking for a revision file system


I'm looking for a filesystem (working through FUSE is fine) that keeps revisions of files (or anything else). It would conceptually resemble a revision control system like CVS, GIT, HG, SVN. But I don't want something that wraps a filesystem on top of one of these revision control systems. I'd rather it operate on top of a regular file tree.

The way I'm thinking about how I might do this if I were to implement it is this. It would be a reflective file system in that it's basis would not be a partition, but instead, would be a file tree on another filesystem. It would store things in that file tree however the design implements it. The stored files could be actual files that are presented, or delta files to save space when large files have small differences, or meta files to manage things.

The mounting of this file system would have at least two different modes:

1. A read-only access to any past revision. The mount would have to specify what revision to access, however revisions are identified. A variant of this mode would present all revisions under a top level pseudo-directory that has names for each revision.

2. A writable current mount mode. Changes made here would create new revisions.

One issue is when do writes and changes increment the version. I seriously doubt anyone wants a new version triggered when one block of a file gets updated. Even when a file being written or updated is closed would be excessive. The revision increment should be roughly equivalent to a complete check-in on a typical revision storage system. An unmount after any change should certainly be the minimum to increment the revision. But it might be desired to leave it mounted across an increment, so some means to force an increment would be good. Maybe "mount -o remount,revisionincrement=yes /mnt/revfs" would be good enough.

Note that this would not be a distributed revision control system. There would be no check-out (that can be changed and later checked back in). Maybe that could also be done, but I would see that as complicated beyond what I would need this kind of thing for. I don't want this as something to replace a revision control system.

Has anyone seen anything like this? Would it have any uses to anyone other than me? One use I'd put it to is as the target when I make backups of other systems via rsync.
 
Old 07-04-2009, 07:52 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 27,457
Blog Entries: 54

Rep: Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897Reputation: 2897
Is there nothing at http://sourceforge.net/apps/mediawik...ingFileSystems? Not FUSE, but how about http://www.nilfs.org/en/?
 
Old 07-04-2009, 10:02 PM   #3
cmdln
Member
 
Registered: Apr 2009
Location: Lawrence, KS
Distribution: Debian, Centos
Posts: 102
Blog Entries: 1

Rep: Reputation: 24
Although I have no experience with them there is svnfs http://www.jmadden.eu/index.php/svnfs/ and gitfs http://www.sfgoth.com/~mitch/linux/gitfs/.
 
Old 07-05-2009, 01:01 AM   #4
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Original Poster
Rep: Reputation: 115Reputation: 115
Quote:
Originally Posted by unSpawn View Post
I had not found that list. There are a couple that are potential candidates there. But they seem to handle accessing the old versions in an awkward way. Still worth investigating. NILFS also looks interesting, but being a core filesystem, it has the risk of development at that level. I want to use one that has its storage on an existing filesystem (either via FUSE or directly).

Quote:
Originally Posted by cmdln View Post
Although I have no experience with them there is svnfs http://www.jmadden.eu/index.php/svnfs/ and gitfs http://www.sfgoth.com/~mitch/linux/gitfs/.
Those work on top of existing revision control systems SVN and GIT. That's not the direction I want to go. This will involve many terabytes of data, primarily from rsync backups of other servers.
 
  


Reply

Tags
filesystem, fuse


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
svn restore directory to a revision also removing files not part of revision Four Linux - Software 1 03-03-2009 04:18 PM
Document Revision / Management System spikeymike Linux - Server 2 12-12-2006 02:16 PM
Revision system w. full web client jnusa Linux - Server 0 11-05-2006 02:18 PM
make-kpkg --revision, deb file naming convention? haertig Debian 10 07-07-2006 04:31 PM


All times are GMT -5. The time now is 03:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration