Differences between revisions 12 and 16 (spanning 4 versions)
Revision 12 as of 2006-02-05 13:33:44
Size: 1223
Comment:
Revision 16 as of 2006-06-11 19:34:22
Size: 1270
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, the only problem is new file/directory creation which I will fix soon... This is my effort to create a unionfs filesystem implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, the only problem is new file/directory creation which I will fix soon...
Line 6: Line 6:

[[GoogleAd()]]
Line 29: Line 31:
[[GoogleAd()]]
Line 31: Line 35:
 * Latest version: 0.10 (released 2006-02-01)  * Latest version: 0.11 (released 2006-06-11)

Foreword

This is my effort to create a unionfs filesystem implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. Currently it's almost fully usable, the only problem is new file/directory creation which I will fix soon...

I'm open to patches, suggestions, whatever (at radek@podgorny.cz)...

GoogleAd()

Why choose this stuff

  • The filesystem has to be mounted after the roots are mounted when using the standard module. With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly
  • You get caching which speeds things up a lot for free
  • You get nice stats (optional)

Why NOT choose it

  • Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner

Available parameters

  • --roots=/root1,/root2

  • --stats

TODO

  • Add support for creating directories
  • Add support for choice which roots are read-only and which are not
  • Add cache controls
  • Handle writing to /stats intelligently

GoogleAd()

Download