Foxing aspires to be an eBPF-powered replication engine for Linux filesystems(codeberg.org)
codeberg.org
Foxing aspires to be an eBPF-powered replication engine for Linux filesystems
https://codeberg.org/aenertia/foxing
6 comments
It reads to me like encryption is handled one layer below this by NFS. I would naively assume this should be set up with external changes disallowed since it is capturing and replaying fs events.
I would love to see a replacement for syncthing though. Something with less config knobs, that 'just works' and handles conflicts more intelligently.
I would love to see a replacement for syncthing though. Something with less config knobs, that 'just works' and handles conflicts more intelligently.
How does it compare to drbd?
"Distributed Replicated Block Device (DRBD)[3] is a distributed replicated storage system for the Linux platform. It mirrors block devices between multiple hosts"
Which I think may be technology used by clouds
"Distributed Replicated Block Device (DRBD)[3] is a distributed replicated storage system for the Linux platform. It mirrors block devices between multiple hosts"
Which I think may be technology used by clouds
How would you replicate:
rsync -avz -e "ssh" user@remote_host:/path/to/source/ /path/to/destination/
Something like this? fxcp snap export /path/to/source/ | ssh user@remote_host -t 'fxcp snap import /path/to/destination/'
Something like this? fxcp snap export /path/to/source/ | ssh user@remote_host -t 'fxcp snap import /path/to/destination/'
This is similar to Dell EMC RecoverPoint which duplicates every block write to a backup target.
No, Foxing is one of my favorite indie-rock bands from the St. Louis area.
Anyways, some hopefully constructive questions that I don't see in the readme:
* Is sync done in cleartext? (Or am I misunderstanding the model and this expects you to handle the network layer yourself with eg. NFS?)
* How are conflicts handled?
* Actually, in general where does this land on CAP? (There's a section titled "Consistency" but it doesn't really answer what I want to know)
> If enable_versioning is active, the daemon creates zero-cost reflink snapshots on fsync:
* How does it handle filesystems that doesn't have that feature? (XFS and BTRFS are easy, but this says it supports ext4)
(And to be clear, none of these are meant as criticisms of the actual software; they're things that the user should know the answer to, not questions that have to have a specific answer)