Longhorn VS Seaweed FS

I'm looking forward to Longhorn[1] taking advantage of this technology. [1]: https://github.com/longhorn/longhorn. - Source: Hacker News / 3 months ago

What backup store you were using? S3 or NFS? Have you tried to report your issues to https://github.com/longhorn/longhorn? Longhorn maintainers/contributors will definitely help with any issues reported by the community. Source: 10 months ago

ChubaoFS - distributed file system and object storage Longhorn - Cloud-Native distributed block storage built on and for Kubernetes OpenEBS - Kubernetes native - hyperconverged block storage with multiple storage engines Rook - Storage Orchestration for Kubernetes SeaweedFS - Distributed file system supports read-write many volumes TiKV - Distributed transactional key-value database Velero - Backup... - Source: dev.to / about 2 years ago

They've also got Longhorn, a distributed container-attached storage solution that's very simple to understand and easy to deploy. Performance is another thing but that's the same with all of the general networked storage solutions (Ceph included). Rancher's got a well deserved good impression in my mind, though early on I avoided it since it seemed like they were building a walled garden. [0]:... - Source: Hacker News / over 2 years ago

Feel free to reach out to us in CNCF Slack channel #longhorn or Rancher user slack channel #longhorn-storage, or file an issue in github.com/longhorn/longhorn . We've dedicated engineers every week to help the community members. Source: over 2 years ago

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet. Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing I've actually been looking for more open alternatives, but haven't found much. Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively:... - Source: Hacker News / 4 months ago

Wireguard + GUI: https://github.com/wg-easy/wg-easy Backups of mail accounts: https://www.offlineimap.org Cloud storage for phones: http://nextcloud.com Mirroring podcasts locally: https://github.com/akhilrex/podgrab My own matrix instance: https://matrix-org.github.io/dendrite/ Backups: https://restic.net Media Management: https://jellyfin.org Relay only tor help: https://www.torproject.org S3 compatible storage:... - Source: Hacker News / 5 months ago

JuiceFS is mostly POSIX compatible, but there are important caveats to that like no ACL, copying files changes their mtime (which impacts backup tools), has "close-to-open" consistency (which makes it dangerous for log appenders). Choosing an appropriate solution in this space still depends on what you need to do with the storage, and some options are MooseFS https://github.com/moosefs/moosefs, Curve... - Source: Hacker News / 10 months ago

Supabase-Storage uses an S3 compatible API and is ultimately just middleware for it. So, the redundancy would be at the storage backend systems. Seems like the majority of s3 compatible selfhosted systems are built for redundancy/high-availability. With only a brief read of docs, and in no particular order: Https://garagehq.deuxfleurs.fr/documentation/quick-start/ Https://github.com/seaweedfs/seaweedfs CEPH... Source: 11 months ago

Adopted SeaweedFS few months back. Never looked back since then. It's fast even on HDD disks. https://github.com/seaweedfs/seaweedfs#introduction. - Source: Hacker News / about 1 year ago