[lkml]   [2005]   [Mar]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectProposal for new (meta) filesystem
Dear fellow Linux-kernel maillist users,

I want to present a new (meta) filesystem proposal to you, to consider.
The filesystem is supposed to be optimized for useage of business filesystems,
mailservers, and other filesystems with an above average amount of repetitive
- Depending on the implementation on block level or on file level (as meta
system): Copy on change of the block or the file.
- Meta database with file features like name, permissions, and checksum per
- The files itself will not be visual to the users, and will not have an owner
(not even nobody). The files will only be accessible through references to
the files.
- The changes are recorded as change on the previous file ala LVM methods but
then per user or group. The changes do not mean that there is an old version
which can be accessed, for the user accessing that file, there is just one
- The changes are kept in a seperate part of the filesystem, which is a
reserved percentage of the diskspace, but which can be stretched by the
filesystem of there are more changes then expected. The changes are kept in a
database like system.
- There is only one change record per file per user/group combination. So in
case of copy of an already changed file, the file will be made permanent, and
the copy will get a reference to this new permanent file.
- Deletion of the source file will be virtual as long as it has references to

Files with different names, dates etc, but with the same binary content will
be stored only once this way. From the outside nobody will see that this
happens, backup programs will make a normal backup.
du should report the virtual used space while df should report the virtual
used space, the optimized use and the real free blocks.

Any more ideas/comments?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-04-06 13:30    [W:0.034 / U:11.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site