trapexit

Generally speaking mergerfs doesn't control anything regarding permissions. The kernel does. mergerfs returns back the permissions and user:group and the kernel does the rest. I'll have to dig deeper into...

They have explicitly written a lot of special code just for GlusterFS which is a little unnerving. They modify the FUSE protocol so it would require a custom build of...

You can look at the IS_GLUSTER_FS macro. It checks to see if the subtype is "glusterfs".

That part is trivial. It would simply have to change from "mergerfs" to "glusterfs" but on the whole there is more complicated. They changed the FUSE protocol. I'd need to...

I've talked about this a number of times if you look through the tickets. Might have mentioned it in the docs too but don't remember. The problem is that, IMO,...

> For reading, mergerfs has everything in place, no (e.g., read youngest mtime, etc.)? Depends on the usecase. Some people want[ read HA](https://github.com/trapexit/mergerfs/tree/read-failover2) where a read failure results in a...

> Very true. So what would be the first step towards designing all this? Writing down all the edge cases? Decide on a fault model? I suppose. All those questions...

I'd prefer a description of the problem and not the solution. There are lots of way to get redundancy and duplication. Creating a fake raid1 kind of thing really isn't...

I understand what you're asking for but I'm not sure I understand your proposal. There is no such thing as a 'branch type'. What you're asking for is per directory...

> The docs referred to 'branch type' regarding RO/RW/NC. But whatever, the important thing is that we understand each other. That's a typo. It should say "mode". I'll fix that....