Re: Versioning file system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Matthew> On Tue, Jun 19, 2007 at 04:34:42PM -0400, John Stoffel wrote:
>> >>>>> "Jack" == Jack Stone <jack@xxxxxxxxxxxxxxxxxxxxxxx> writes:
>> 
Jack> The whole idea of the file system is that it wouldn't return the
Jack> file in the file listing. The user would have to know that the
Jack> file system was versioning to access the older versions as they
Jack> would explicitly have to request them.
>> 
>> So tell me what happens when I do:
>> 
>> touch foo:121212121212

Matthew> You create a new file called 'foo:121212121212'.  If you then
Matthew> modify it, you could access the old version as
Matthew> foo:121212121212:0.

Sure, I knew that, I was trying to push the boundaries a bit here with
magic version filenaming conventions to show that it won't scale.
Heck, trying to figure out what:

	touch foo::::::::::::::::::::::

does would be interesting, and would the filesystem parsing code
handle that case?  

Matthew> (The .snapshot directory makes more sense than magic names,
Matthew> since you can see what versions of a file are available
Matthew> without a special tool).

I agree 100%, it's a much better solution, though it has it's own
problems, esp over NFS and getting back to your original parent
directory properly can be painful.

John

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux