>
> I'm going to take a wild guess here and describe in my words what I
>
think you want:


>  * You want two file systems, one locally and one remote
>  * You want to have an union file system (like unionfs), that "merges"
>    the two file systems, and where files from the local fs take
>    precedence.
>  * You want writes to the union to be propagated to both the local and
>    remote fs
>  * Occasionally, you want to delete files from the local fs that have
>    not been accessed for a while
>
> Is that correct? In that case (as the description already implies), I
> would take a look at the various union/overlay file systems to see if
> any of them already does what you want. The only thing that might be
> missing is the ability to write to both backing file systems. You could
> either hack that yourself, or periodically run rsync from the local
> backing filesystem to the remote backing filesystem. For the expiration,
> a cron-job would do.
>

You definitely got the gist, except for two pieces, both of which I've
found lacking in other solutions (including unionfs), and both of which are
at the core of my desire:

   - reads from the remote fs should populate the local fs
      - should be easy to do this wherever write propagation is implemented
   - *the mount point of the merged fs should be the same as the root of
   the local fs*

The last point, the one you mentioned is impossible, is the lynchpin. After
reading FUSE's docs, it would seem possible to do so by modifying the
kernel extension to not just intercept and forward system calls to paths
beneath the mounted FUSE subtree, but to support interacting with local
"on-disk" paths. That, of course, rests upon the assumption that the kernel
can interact with the "real" filesystem directly and bypass the FUSE
filesystem. If that is not possible, I would love to know why!

Thank you SO MUCH, Nikolaus :)

Cameron

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to