mirror of
https://github.com/versity/scoutfs.git
synced 2025-12-23 05:25:18 +00:00
f2646130ae
scoutfs_alloc_prepare_commit() is badly named. All it really does is put the references to the two dirty alloc list blocks in the allocator. It must allways be called if allocation was attempted, but it's easier to require that it always be paired with _alloc_init(). If the srch compaction worker in the client sees an error it will send the error back to the server without writing its dirty blocks. In avoiding the write it also avoided putting the two block references, leading to leaked blocks. We've been seeing rare messages with leaked blocks in tests. 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