mirror of
https://github.com/versity/scoutfs.git
synced 2026-01-03 10:55:20 +00:00
102899290e
The server's srch commit error warnings were a bit severe. The compaction operations are a function of persistent state. If they fail then the inputs still exist and the next attempt will retry whatever failed. Not all errors are a problem, only those that result in partial commits that leave inconsistent state. In particular, we have to support the case where a client retransmits a compaction request to a new server after a first server performed the commit but couldn't respond. Throwing warnings when the new server gets ENOENT looking for the busy compaction item isn't helpful. This came in tests as background compaction was in flight as tests unmounted and mounted servers repeatedly to test lock recovery. 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