Differences between revisions 30 and 52 (spanning 22 versions)
Revision 30 as of 2007-01-27 12:44:28
Size: 1776
Comment:
Revision 52 as of 2012-02-02 12:37:31
Size: 1592
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Foreword = = unionfs-fuse =
Line 3: Line 3:
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... This is my effort to create a unionfs filesystem implementation which is way more flexible than the current in-kernel unionfs solution.
Line 5: Line 5:
I'm open to patches, suggestions, whatever (at radek@podgorny.cz)... I'm open to patches, suggestions, whatever... The preferred way is the mailing list at {{{unionfs-fuse (at) googlegroups (dot) com}}} or see [[http://groups.google.com/group/unionfs-fuse|unionfs-fuse on Google Groups]].
Line 7: Line 7:
[[GoogleAd()]] If you want to contact me and me only see the [[Contact]] page on how to reach me...

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...

<<GoogleAd>>
Line 14: Line 18:
 * Advanced features like copy-on-write and more
Line 17: Line 22:
 * Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner  * 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 19: Line 24:
== 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
}}}

== TODO ==

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

[[GoogleAd()]]
<<GoogleAd>>
Line 44: Line 28:
If you use the software and like it, please consider a donation (provided by Pay''''''Pal)...

[[PayPalDonation()]]
If you use the software and like it, please consider a donation [[Donation]]...
Line 50: Line 32:
 * Latest version: 0.16 (released 2007-01-26)  * Latest version: 0.25 (released 2012-02-02)
Line 52: Line 34:

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

 *
http://hg.podgorny.cz/unionfs-fuse
 * Repository location: http://hg.podgorny.cz/unionfs-fuse (Mercurial)

unionfs-fuse

This is my effort to create a unionfs filesystem implementation which is way more flexible than the current in-kernel unionfs solution.

I'm open to patches, suggestions, whatever... The preferred way is the mailing list at unionfs-fuse (at) googlegroups (dot) com or see unionfs-fuse on Google Groups.

If you want to contact me and me only see the Contact page on how to reach me...

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 Donation...

Download