mirror of
https://github.com/versity/scoutfs.git
synced 2026-02-10 12:40:09 +00:00
e54f8d3ec0
Errors from lock server calls typically shut the server down. During normal unmount a client's locks are reclaimed before the connection is disconnected. The lock server won't try to send to unmounting clients. Clients whose connections time out can cause ENOTCONN errors. Their connection is freed before they're fenced and their locks are reclaimed. The server can try to send to the client for a lock that's disconnected and get a send error. These errors shouldn't shut down the server. The client is either going to be fenced and have the locks reclaimed, ensuring forward progress, or the server is going to shutdown if it can't fence. This was seen in testing as multiple clients were timed out. Signed-off-by: Zach Brown <zab@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