GlusterFS
Tahoe-LAFS
Our great sponsors
GlusterFS | Tahoe-LAFS | |
---|---|---|
19 | 9 | |
4,478 | 1,277 | |
1.6% | 0.5% | |
6.4 | 9.6 | |
4 days ago | 27 days ago | |
C | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GlusterFS
-
Tell HN: ZFS silent data corruption bugfix – my research results
https://github.com/gluster/glusterfs/issues/894
And apparently apart from modern coreutils using that, it is mostly gentoo users hitting the bugs in lseek.
-
Linux deserves a better class of friends
This Product Appendix does not apply to online service offerings managed by Red Hat or generally available open source projects such as www.wildfly.org, www.fedoraproject.org, www.openstack.redhat.com, www.gluster.org, www.centos.org, okd.io, Ansible Project Software or other community projects.
-
Which distributed filesystem to use on a 4 node cluster?
Just because Red Hat will stop selling commercial support for their product, does not mean GlusterFS itself is dying. It's an open source project like any other - https://github.com/gluster/glusterfs
-
Setting up a 2 node distributed network share
https://www.gluster.org/ Is the way to do this across nodes
-
System Design: Netflix
This allows us to fetch the desired quality of the video as per the user's request, and once the media file finishes processing, it will be uploaded to a distributed file storage such as HDFS, GlusterFS, or an object storage such as Amazon S3 for later retrieval during streaming.
-
What's the best way to periodically sync two remote servers?
GlusterFS
-
System Design: The complete course
But where can we store files at scale? Well, object storage is what we're looking for. Object stores break data files up into pieces called objects. It then stores those objects in a single repository, which can be spread out across multiple networked systems. We can also use distributed file storage such as HDFS or GlusterFS.
-
First Apartment and First Homelab
GlusterFS - same as above (https://www.gluster.org/)
-
Multiple DS units acting as one?
What you look for is a clustered file system. Like https://www.gluster.org/. As long as all units are closeby with low latency there are a couple solutions that allow you to create distributed storage solutions of various kinds. Key value stores applenty, clustered file systems that pretent to be one file system etc. If you have geographically distributed solutions with high latencies it becomes harder. Most open source systems don't work really well in this scenario. There were a couple attempts like Hydrabase but they didn't go so far. It normally is solved by doing two clusters and then replicate between them.
-
Upload pdf file to mongodb atlas
I'd imagine most managed service providers are going to require a credit card, though most of them have a free tier. If you want to take an unmanaged approach, maybe look into Gluster. I've used it before and never had issue with it, but I also had an infrastructure team that set it up, so I'm not familiar with the challenges that way: https://www.gluster.org/
Tahoe-LAFS
-
Distributed Network File System
You could also look at Tahoe-LAFS which I keep meaning to try: https://tahoe-lafs.org/
-
Merging with diff3: the “three-way merge”
Then there are Darcs and Pijul, which use a theory of patches.
So Pijul manages to have lossless merges by actually storing a directed graph (though of course, you will still need to decide how to flatten that into a displayed file) :
https://jneem.github.io/pijul/
And because uses more information about the history, it is able to do smarter merges (if I am not mistaken, even compared to the OP ?) :
https://tahoe-lafs.org/~zooko/badmerge/simple.html
https://pijul.org/faq
- The Tahoe-LAFS decentralized secure filesystem Version 1.17.0
-
The Underwhelming Impact of Software Engineering Research (April 2022)
Good news for you: I'm well on the way to solving the problem of better code merging. Specifically, the algorithms I am developing appear to be able to do a correct merge on both [1] and [2]. They also appear capable of merging binary data.
The tradeoff is that people need to write some code to tell the VCS about the format of each binary file type or semantics of each programming language.
The biggest problem is that, like Rust, a new VCS has to be well-executed to make its innovation stick. We'll see if I succeed.
[1]: https://tahoe-lafs.org/~zooko/badmerge/simple.html
[2]: https://tahoe-lafs.org/~zooko/badmerge/concrete-bad-semantic...
- Anybody know of server selfhosted software that can unify or pool multiple cloud storage accounts ?
-
Nextcloud listened to Linus "Unraid Friends" idea (maybe) and implemented P2P backup in Nextcloud Hub II !
u/nextale shared a couple options: Tahoe-LAFS , Duplicati an Retroshare
-
Anything similar to StorJ? For self hosted purposes?
Only thing that comes close is https://tahoe-lafs.org
-
About Linus' WAN show notes about backups and losing data: I think there does exists something that he describes that fits the bill
There is Tahoe-LAFS which is decentralized open-source software where you can add remote storage servers (for example on a friends server) to store your data but the server does not have the encryption keys. Your data is encrypted before it leaves your computer (they call it "Least Authority File System" or LAFS because only you hold the keys, the storage servers just store the data). The data is encrypted in-transit and on-rest and supports multiple nodes so even if one of the servers burn down you still have the same data elsewhere. I believe they offer a commercial storage solution but you and your friends could install it for yourselves and run a closed network.
-
DEFFS - my custom FUSE filesystem
do you know https://tahoe-lafs.org? your goals sound similar.
What are some alternatives?
minio - The Object Store for AI Data Infrastructure
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
lizardfs - LizardFS is an Open Source Distributed File System licensed under GPLv3.
Ceph - Ceph is a distributed object, block, and file storage platform
Seaweed File System - SeaweedFS is a fast distributed storage system for blobs, objects, files, and data lake, for billions of files! Blob store has O(1) disk seek, cloud tiering. Filer supports Cloud Drive, cross-DC active-active replication, Kubernetes, POSIX FUSE mount, S3 API, S3 Gateway, Hadoop, WebDAV, encryption, Erasure Coding. [Moved to: https://github.com/seaweedfs/seaweedfs]
btrfs - Haskell bindings to the btrfs API
Nextcloud - ☁️ Nextcloud server, a safe home for all your data
MooseFS - MooseFS – Open Source, Petabyte, Fault-Tolerant, Highly Performing, Scalable Network Distributed File System (Software-Defined Storage)
Camlistore - Perkeep (née Camlistore) is your personal storage system for life: a way of storing, syncing, sharing, modelling and backing up content.
OpenAFS - Fork of OpenAFS from git.openafs.org for visualization
Filestash - 🦄 A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ...