mirror of
https://github.com/versity/scoutfs.git
synced 2026-04-26 16:15:06 +00:00
658105c77e
To consistentely finalize an open_log_trees _get_log_trees commits a mostly empty copy of the current log_trees at the current nr with the finalized bit set. It then later commits the rest of the current log_trees at the next nr. Splitting this across two commits leaves a window where the persistent version of the items have lost references to some of the structures in the log_trees, particularly the allocators. If we were to crash in this window we'd lose all those structures. This is a conservative change that commits both the finalized current nr and the next nr in one commit. It avoids changing too much of the code flow to only fix this one problem. 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