mirror of https://github.com/versity/scoutfs.git synced 2026-08-16 04:06:39 +00:00

T

Auke Kok 205cfbdf4a Don't shut down the server when fencing a rid twice

A node only needs to be fenced once, but scoutfs_fence_start() can be
called for the same rid more than once. When a new leader starts it
fences the previous leader as it removes it from the quorum
(quorum_block_leader), and that same rid can also be a mounted client
that then fails to recover within the timeout (client_recovery).

The second fence call collides on that name, sysfs returns -EEXIST,
and the error is propagated to fence_pending_recov_worker() which
treats any error as fatal and shuts the server down. On the next
mount a new leader hits the same stale set and the same collision,
so the filesystem can never finish recovery.

  Jun 15 09:22:35 kernel: scoutfs f.000000.r.222222: fencing previous leader f.000000.r.111111 at term 183942 in slot 3 with address x.x.x.x:6000
  Jun 15 09:22:36 scoutfs-fenced[9194]: [2026-06-15 09:22:36.588037842] server f.000000.r.222222 fencing rid 1111111111111111 at IP x.x.x.x for quorum_block_leader
  Jun 15 09:23:09 kernel: scoutfs f.000000.r.222222 error: 30000 ms recovery timeout expired for client rid 1111111111111111, fencing
  Jun 15 09:23:09 kernel: sysfs: cannot create duplicate filename '/fs/scoutfs/f.000000.r.222222/fence/1111111111111111'
  Jun 15 09:23:09 kernel: scoutfs f.000000.r.222222 error: fence returned err -17, shutting down server

Check the list for the rid and skip the duplicate before creating
sysfs. A pending fence can be freed once it is on the list, so a new
fi->mutex serializes creation against the freeing path: the duplicate
check, sysfs create, and list insert run as a unit, and a fence becomes
visible on the list only once it is fully built. scoutfs_fence_free()
and scoutfs_fence_stop() take the same mutex around removing a fence
and tearing it down, and scoutfs_fence_destroy() drains through
fence_stop() rather than walking the list unlocked.

Signed-off-by: Auke Kok <auke.kok@versity.com>

2026-07-23 09:14:59 -07:00

kmod

Don't shut down the server when fencing a rid twice

2026-07-23 09:14:59 -07:00

tests

Remove format-version 1 test.

2026-06-05 09:49:45 -07:00

utils

Guard log_merge, srch_root, and mounted_client item printers

2026-07-23 09:14:31 -07:00

.gitignore

Initial commit

2020-12-07 09:47:12 -08:00

Makefile

Add simple top-level Makefile

2020-12-07 10:39:20 -08:00

README.md

Update README.md

2021-11-05 11:16:57 -07:00

ReleaseNotes.md

v1.32 Release

2026-06-03 11:34:21 -07:00

README.md

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