mirror of
https://github.com/versity/scoutfs.git
synced 2026-05-12 15:41:28 +00:00
e011c80452
There is no reason to fence any connection that hasn't sent a valid greeting, since they haven't progressed far enough for it to make sense. Skip the fence call for these connections and let the existing destroy path tear them down. Any real client will reconnect. server_notify_down() previously treated any zero rid teardown as the listening socket going down and called stop_server(). That's correct for the listener legitimately, but not for any conn that never completed a greeting. Adds a test that sends a short garbage payload to each quorum port and verifies that no greeting-less connection remains past the reconnect timeout (20s) and that the filesystem still works afterwards. 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