Differences between revisions 38 and 40 (spanning 2 versions)
Revision 38 as of 2007-12-05 17:09:49
Size: 1420
Comment:
Revision 40 as of 2008-05-28 12:24:42
Size: 1404
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
[[GoogleAd()]] <<GoogleAd>>
Line 16: Line 16:
 * Advanced features like copy-on-write and more
Line 21: Line 22:
== TODO ==

 * Handle writing to /stats intelligently

[[GoogleAd()]]
<<GoogleAd>>
Line 31: Line 28:
[[PayPalDonation()]] <<PayPalDonation>>
Line 37: Line 34:
 * Repository location: http://hg.podgorny.cz/unionfs-fuse (Mecrurial)  * Repository location: http://hg.podgorny.cz/unionfs-fuse (Mecurial)

unionfs-fuse

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.

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

If you've sent me something and think it takes me too long to answer, go check UndeliverableMail page. I might have problems sending mail to you...

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)
  • Advanced features like copy-on-write and more

Why NOT choose it

  • Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner (well, actually I've made some tests and the hard-drives seem to be the bottleneck so the speed is fine, too)

Donation

If you use the software and like it, please consider a donation (provided by PayPal)...

Download