mirror of
https://github.com/versity/scoutfs.git
synced 2026-09-29 11:15:47 +00:00
Zach Brown
af893e8888
As totl items are merged they're supposed to be dropped if both their count and total are zero. It's a slight mechanical simplification because it means deletions can emit the same delta items as non-deletion changes. The btree code that does this has a day-one bug where it clobbers the return value of the delta combination before checking it. The resulting items are still correct but they don't need to exist. Readers ignore them. The easy fix doesn't clobber the delta combination result in the merge loop so the zero items won't be written by the merge. Since these were ignored by readers there won't be a user-facing change. We'll do less work in the future as zero items aren't written and the next merge will drop all the existing items that were left behind by previous merges. 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