On Nov 11 2015, Cameron Boehmer <[email protected]> wrote:
> I arrived here wanting to mount a filesystem that can expose
> and modify on-disk paths beneath its mount point.
Sounds like ext4 will satisfy all your needs then :-).
> If you're curious *why* I want such a thing, well, as I've said, I'd like
> to write user-space filesystems that leave their contents "in place" after
> the FUSE process terminates.
Which is a bad idea for several reasons:
* If the file system crashes, the mountpoint will become inaccessible
(rather than revert to whatever the mount was shadowing)
* If the file system terminates regularly (and unmounts), applications
that already opened files or directories on the mountpoint still hang
or crash.
* From a user perspective, you would never be able to tell if you are
working through the userspace file system or not (which, dependending
on the purpose of the userspace file system easily nullifies the
advantage. E.g. if you want to store the data in two places for
redundancy you could not actually rely on it).
* If the purpose is to keep the data stored in two places (which I
believe you want to do), you need additional complexity to handle
synchronization issues. Otherwise you cannot tell if a file has been
deleted in one place (and should be deleted in the other) or if it
has been created in the other.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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.
