mirror of
https://github.com/versity/scoutfs.git
synced 2026-05-12 23:51:30 +00:00
f604bb4b77
Add last_user_pid[mode] and last_user_ino[mode] arrays to scoutfs_lock, filled in at the granted-mode path alongside the existing counts. The inode is passed by callers for all per-inode cases, and set to 0 for others. PID is from the current task. The client_locks line is expanded with "ino: rd I wr I wo I pid: rd P wr P wo P". Existing users:/waiters: field positions are unchanged. A simple test case demonstrates the functionality for the two simple inode/non-inode case, and for a contended lock case (multiple rd/wr lock holders). Signed-off-by: Auke Kok <auke.kok@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