Morph into a network filesystem

[droundy]

I wonder how painful it would be to turn syncer into a network filesystem, ie to enable multiple clients to mount the same filesystem?

This would require coordination and locking, and a host of other details, but it sounds like syncer could be a nice basis for such a system.

[pedrocr]

Not only is it possible I have a design in my head for it. Still thinking through the details.

[droundy]

I've also been thinking about designing such a filesystem. I've been thinking I'd like a Raft-based set of servers.

…

On Sun, Feb 18, 2018, 1:49 PM Pedro Côrte-Real ***@***.***> wrote: Not only is it possible I have a design in my head for it. Still thinking through the details. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIZKY58Mh7qkty6yr5e2k7EezELne66ks5tWJsHgaJpZM4SJ20B> .

[pedrocr]

Here's my current thinking around it:

https://github.com/pedrocr/syncer/blob/de60108780169cf2d2a66c85be84ba904216738c/TODO.md#multi-master-readwrite

I like the property of being able to have the central server still be a dumb NAS with just ssh/rsync. I do want to have replication between 2 or more NAS servers though for redundancy and performance if you have one in each LAN you frequent.

[pedrocr]

Feel free to show up in #chimper if you'd like to discuss this more. I personally don't have as much of a use case for multi-master read/write (as I use a single laptop as my working machine at all times) but I'm enjoying the challenge of thinking through how to do it.

[ehiggs]

I wonder how painful it would be to turn syncer into a network filesystem, ie to enable multiple clients to mount the same filesystem?

Maybe it would make sense to support syncthing's protocol as a first step. Or did you mean implementing an NFS gateway?

[pedrocr]

@ehiggs as far as I know syncthing has semantics that are quite far away from POSIX. I actually wrote syncer because syncthing didn't work for me. I also really like the simplicity of the "server" just being any rsync end-point but I that may end up being a more power-user and less user-friendly choice. A simple network backend done by syncer itself would be fairly easy to do though. I'm almost done implementing the multi-master read/write support so hopefully the 0.6 release is soon and people can start testing if it works for their use case as well.

[AlexMikhalev]

I found a filesystem that is complementary to your design and seems to fit all other requirements I can think of https://github.com/chrislusf/seaweedfs/wiki/Production-Setup