Differences between revisions 28 and 34 (spanning 6 versions)
⇤ ← Revision 28 as of 2006-10-13 23:47:52 →
Size: 1963
Editor: RadekPodgorny
Comment:
← Revision 34 as of 2007-08-09 12:01:28 → ⇥
Size: 1406
Editor: RadekPodgorny
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Foreword = = unionfs-fuse =
Line 17: Line 17:
 * Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner

== Usage ==

{{{
unionfs [options] root[:root...] mountpoint
The first argument is a colon separated list of directories to merge

general options:
    -o opt,[opt...] mount options
    -h --help print help
    -V --version print version

UnionFS options:
    -o stats show statistics in the file 'stats' under the mountpoint
}}}		  * 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)
Line 36: Line 21:
 * Add support for choice which roots are read-only and which are not
 * Add cache controls
Line 50: Line 33:
 * Latest version: 0.15 (released 2006-08-07)  * Latest version: 0.18 (released 2007-08-09)
Line 53: Line 36:
If you want to follow the development closely, see my experimental mercurial repository at: If you want to follow the development closely, see my mercurial repository at:
Line 56: Line 39:

My older tinyrcs repository is at:

 * http://podgorny.cz/~radek/rep/unionfs-fuse/

(tinyrcs is my currently-under-development revision control system) -> ["TinyRCS"]

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. Currently it's almost fully usable, will only minor convenience issues to be fixed...

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 (well, actually I've made some tests and the hard-drives seem to be the bottleneck so the speed is fine, too)

TODO

  • Handle writing to /stats intelligently

GoogleAd()

Donation

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

PayPalDonation()

Download

If you want to follow the development closely, see my mercurial repository at: