mirror of
https://github.com/versity/scoutfs.git
synced 2026-06-09 21:22:36 +00:00
Auke Kok
c137637007
I thought this would just work between ipv4 and ipv6 based quorum members, but it turns out it will only work one way by default. While we could make this work (multiple sockets, special sockopts) it is highly unlikely and very undesirable. Much stronger feels to just disallow it explicitly and reject mixed v4/v6 configurations outright (mkfs/change-quorum, and mount) to avoid this. I can't imagine this doing any good for users' fencing setups. The test cases added validate the 2 easy userspace checks. The mount check isn't easily testable because we disallow userspace from creating such a failure path. One additional test section tests the migration path from v4->v6->v4 so there's at least some test that checks that this actually works. Signed-off-by: Auke Kok <auke.kok@versity.com>
Introduction
scoutfs is a clustered in-kernel Linux filesystem designed to support large archival systems. It features additional interfaces and metadata so that archive agents can perform their maintenance workflows without walking all the files in the namespace. Its cluster support lets deployments add nodes to satisfy archival tier bandwidth targets.
The design goal is to reach file populations in the trillions, with the archival bandwidth to match, while remaining operational and responsive.
Highlights of the design and implementation include:
- Fully consistent POSIX semantics between nodes
- Atomic transactions to maintain consistent persistent structures
- Integrated archival metadata replaces syncing to external databases
- Dynamic seperation of resources lets nodes write in parallel
- 64bit throughout; no limits on file or directory sizes or counts
- Open GPLv2 implementation
Community Mailing List
Please join us on the open scoutfs-devel@scoutfs.org mailing list hosted on Google Groups