zfs: the module owns a node's ZFS and changes nothing unset; pacman declares its config before its package (issue 1979) #676

2026-11-13T01:07:00Z

mesh-tools commented

2026-11-13 01:07:00 +00:00

Issue 1979, ADR 0679 (v23), design 42 milestone zfs-owns-zfs §6-§31 and the main file's The zfs module; lead answers A-1..A-46 (hq 03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-tools, mesh-host and mesh-delivery.

Z0 2b699d40: pacman's config file before its package (A-26).
modules/zfs: packages, pool renamed from scrub-pool, every new value not managed until set; the config file ${config-json}; zfs.conf, ZED folder, units; the apply (properties, cache and log devices by stable name, ARC, /etc/hostid with zgenhostid guarded by the pool's label and read back); the scheduled run (scrub, trim, ZFS snapshots recorded in the ledger snapshots); hand acts; the follower (findings in the state list's findings, A-46); tools; health; leaving; the call-site test of ADR 0679 §7/§19; a user and process zfs-keeper holding the module's one process bus account, reached by the root processes over a root-only socket (A-37); the tools say every event onto the events stream with mesh/stream.publish (A-42); capabilities stream-publish, bus-state-calls, ledger-calls (A-44).
mesh-conditions: the keeper reads zfs's findings (aa0a472b).
The first check (03f2ebff6ed0) failed in four kinds, fixed here: the findings keeper (aa0a472b, 0041b69d), the keeper tests' temporary directory (8ae4fabf, d1a15ced), the vendor hosts of the package's ZED script as names on purpose (064ebc9b), and a blocking date-bound test in mesh-hand-acts that failed on the trunk too (afa825f9; the kind noted on issue 1878).
88 unit tests, no integration test (§31). The manifest validator at mesh-delivery ad7e5809 accepts zfs, mesh-conditions and pacman.

Before the new version is placed on the home server, the lead moves the pool's name from the assignment to mesh-config (A-1).

Reviewed-by: mesh-code-reviewer of fix-1977@ace at 0041b69d17

Issue 1979, ADR 0679 (v23), design 42 milestone zfs-owns-zfs §6-§31 and the main file's *The zfs module*; lead answers A-1..A-46 (hq 03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-tools, mesh-host and mesh-delivery. - Z0 2b699d40: pacman's config file before its package (A-26). - modules/zfs: packages, `pool` renamed from `scrub-pool`, every new value not managed until set; the config file `${config-json}`; zfs.conf, ZED folder, units; the apply (properties, cache and log devices by stable name, ARC, /etc/hostid with zgenhostid guarded by the pool's label and read back); the scheduled run (scrub, trim, ZFS snapshots recorded in the ledger `snapshots`); hand acts; the follower (findings in the state list's `findings`, A-46); tools; health; leaving; the call-site test of ADR 0679 §7/§19; a user and process `zfs-keeper` holding the module's one process bus account, reached by the root processes over a root-only socket (A-37); the tools say every event onto the events stream with `mesh/stream.publish` (A-42); capabilities `stream-publish`, `bus-state-calls`, `ledger-calls` (A-44). - mesh-conditions: the keeper reads zfs's findings (aa0a472b). - The first check (03f2ebff6ed0) failed in four kinds, fixed here: the findings keeper (aa0a472b, 0041b69d), the keeper tests' temporary directory (8ae4fabf, d1a15ced), the vendor hosts of the package's ZED script as names on purpose (064ebc9b), and a blocking date-bound test in mesh-hand-acts that failed on the trunk too (afa825f9; the kind noted on issue 1878). - 88 unit tests, no integration test (§31). The manifest validator at mesh-delivery ad7e5809 accepts zfs, mesh-conditions and pacman. Before the new version is placed on the home server, the lead moves the pool's name from the assignment to mesh-config (A-1). Reviewed-by: mesh-code-reviewer of fix-1977@ace at 0041b69d173611afb395e7c0f6891b8d89ffe64f

mesh-tools added 29 commits 2026-11-13 01:07:00 +00:00

Z0 pacman-config-first: the pacman module declares its config file before its package 2b699d4046

The apply stops at the first failure and the package fails while the config file is missing (A-26).

Builds: design 42 zfs-owns-zfs §1, A-26

Z5 zfs-config-parse: the config file's values each read in their fixed form 3cb2b83a15

A value of another form is refused before anything is written or run; absent and empty are not managed.

Builds: design 42 zfs-owns-zfs §9, §11, A-15, A-23

Z6 zfs-events-state: each change, refusal and wait said as its event and kept in the state applied 0fa4b5d8e7

Builds: design 42 zfs-owns-zfs §25, §26, A-19

Z7 zfs-apply-properties: pool and dataset properties converged, read back and said a10bf45ed9

Builds: design 42 zfs-owns-zfs §10, §16

Z8 zfs-apply-devices: cache and log devices converged by their stable names, after their checks 2fb1e5c4ea

Builds: design 42 zfs-owns-zfs §17

Z9 zfs-apply-run: the apply holds the lock, waits on a scrub or an unimported pool, and converges the node's id, ARC and pool 1bea6edcb8

Builds: design 42 zfs-owns-zfs §15, §18, A-8, A-16, A-29

Z10 zfs-run: the scheduled run takes the lock, starts a due scrub and trim without waiting, and acts on hand acts 06d83912cd

Builds: design 42 zfs-owns-zfs §20, §24, A-17

Z13 zfs-hand-acts: hand acts write their key and start the run; zfs_snapshot keeps a person's snapshots apart 316039ca95

Builds: design 42 zfs-owns-zfs §23, §24, A-12, A-17, A-18

Z11 zfs-snapshots-take: the run takes its due ZFS snapshots per filesystem and records each in the ledger a357a85faa

Builds: design 42 zfs-owns-zfs §21, §26, A-19, A-20, A-30, A-31

Z12 zfs-snapshots-remove: the run removes surplus scheduled ZFS snapshots only by their own record 23256413de

Builds: design 42 zfs-owns-zfs §22, §26, A-30, A-31

Z14 zfs-follower: the follower starts the apply on the events that end a wait and keeps its findings in its own state dd1a4e083c

Builds: design 42 zfs-owns-zfs §18, §27, A-10, A-16, A-32

Z10 Z12 trim without day or time refused, keep count 0 removes nothing 8aad282e6c

A trim schedule of weekly or monthly with no trim-day or trim-time is one refused value naming it; a keep count of 0 is that kind's none: the existing scheduled ZFS snapshots are kept and a warning names them.

Builds: design 42 zfs-owns-zfs §20, §21, §22, A-33, A-35

Z15 zfs-tools: zfs_config, zfs_snapshots_schedule, zfs_module_events, zfs_snapshots_check and zfs_findings read what the module owns, keeps and says c0067e77fc

zfs_config also says what the module says before it leaves a node (Z17): the next load of the kernel module uses ZFS's defaults, the three units and /etc/hostid stay.

Builds: design 42 zfs-owns-zfs §28, §30, §10, A-31, A-35

Z16 zfs-health: a refused or failed command in the applied state is unhealthy naming its key, and the module's own warnings 97bdb7d656

Builds: design 42 zfs-owns-zfs §29, §15, A-35

Z1 Z2 Z3 zfs-manifest: packages and values, files and units, the apply and the run in the declared order 5ab8bb7e62

The manifest declares zfs-utils and zfs-dkms, renames scrub-pool to pool, and declares every new value not managed until set; its config file is ${config-json}, the options file, ZED's folder, rc, functions, handlers and drop-in each under their condition, the three ZFS units, the apply (run-once, restarted by its config file) and the run before the distribution's scrub and trim timers. One commit: the three subtasks change the one file module.json.

Builds: design 42 zfs-owns-zfs §6, §7, §8, §9, §11, §12, §13, §14, §15, §18, §20, A-1, A-2, A-3, A-7, A-14, A-15, A-16, A-23

Z18 zfs-callsite: the call-site test pins every form of ADR 0679 whole 9116067e11

Renamed TestTheBundleRunsOnlyTheFormsOfADR0679: each root form is held to its whole argument list, no verb the decision never allows, zgenhostid only with the parsed hostid, a device only as cache or log.

Builds: design 42 zfs-owns-zfs §19

Z11 Z12 Z15 the ledger is one instance per dataset and kind, its state a map taken keyed by the ZFS snapshot's name c6844fc951

Builds: design 42 zfs-owns-zfs §21, §22, §26, §28, A-36 (corrects A-30)

A-37 the keeper: the module's one process bus account, a socket only root opens, and the root processes' bus through it ec27f12524

Builds: design 42 zfs-owns-zfs §18, §20, §26, §27, A-6, A-20, A-37

Z4 zfs-manifest-bus: the events stream, states and ledger by template, the keeper as the module's one process bus account 8927d68900

The three root processes declare no bus and reach the keeper's socket; the module invokes the service manager's start. The judge refuses the keeper's bus emits and state until the validator accepts what the module asks for in requires (A-38).

Builds: design 42 zfs-owns-zfs §25, §26, §27, §28, A-6, A-19, A-36, A-37, A-38

Z19 zfs-readme-budget: the README says what the module owns and how it is checked, and the test budget is a test 7831f14a6e

Builds: design 42 zfs-owns-zfs §31, §7, §19, §23

Z19 the budget test does not match its own text 605c1b1ca0

Builds: design 42 zfs-owns-zfs §31

zfs: take out the events stream's max-mib, a bound no design line gives (review finding 3) 008e02afbd

Builds: design 42 zfs-owns-zfs §25

zfs: read an unwritten ledger instance as state null and sequence 0, pass every error up (review finding 2, A-40) 5f372ac63a

Builds: design 42 zfs-owns-zfs A-40

zfs: a follower reaches the keeper's socket on every call, so a keeper up later is used (A-37, reviewer's note) e79392d666

Builds: design 42 zfs-owns-zfs A-37

zfs: the keeper publishes events with an acknowledged JetStream publish on mesh.bus.zfs.events.<kind> (review finding 1, A-41) 87f8c30a09

Builds: design 42 zfs-owns-zfs A-41, §25

zfs: a keeper that does not answer is warned once, and RunKeeper closes its second connection (review round 2 finding 2, A-37) 2d592c63c1

A failed keeper call in a root process (hand acts, forget, Paused, every call) now adds one warning that the bus is
taken as down, instead of being dropped silently. RunKeeper closes the connection acct.Dial opens when the keeper
stops; the message id's comment says it is nanotime-pid.

Builds: design 42 zfs-owns-zfs A-37

zfs: the tools say events with mesh/stream.publish and a hand act hears its event on the events stream (A-42, A-12) 1ff904f101

The tools say every event of §25 (snapshot.taken.person, scrub.requested and the others) with mesh/stream.publish on the
stream events, never stdio.Emit; the hand acts' 30 s wait reads the mark (stream.fill) before the act starts, then
stream.read from the next sequence, for at most HandWait.

Builds: design 42 zfs-owns-zfs §25, §24, lead answers A-42, A-12

zfs: the hand acts answer started at once and the manifest asks stream-publish, bus-state-calls and ledger-calls (A-43, A-44) 58664eee60

Removes streamHear, HandPoll, HandWait and the stream mark; keeps toolEmit.

Builds: design 42 zfs-owns-zfs §24, §25, lead answers A-43, A-44

zfs: declare health on the four running services, README says hand acts answer started

mesh/delivery-group group feature/1979-zfs-owns-zfs rejected: composed together: the checker's verdict at the members' heads (03f2ebff6ed0): unit: mesh-conditi…

Details

mesh/delivery closed: a newer head of the same pull request

Details

mesh/check failed (9): unit: mesh-conditions/cmd/mesh-conditions.TestEveryControllerKindHasItsHome: the rea…; and 8 more | d15502f3650d on 117f933dacf0

d15502f365

Builds: design 42 zfs-owns-zfs §13, §24, lead answers A-45, A-43

mesh-tools commented

2026-11-13 01:07:09 +00:00

Delivery novox/mesh-catalog@0041b69d1736 — merged since 2026-11-13T08:01:05Z

Source — source.main moved to novox/mesh-catalog@32f1566cc8. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group feature/1979-zfs-owns-zfs: novox/mesh-catalog@0041b69d17, novox/mesh-delivery@ad7e580918, novox/mesh-host@96a8690639, novox/mesh-sdk@2895a21e69, novox/mesh-tools@df2162e381

composed together: pass — the checker's verdict at the members' heads (13bf070ecb87)

Transitions

2026-11-13 02:31 (new) → proposed (announced): novox/mesh-catalog#676's head announced
2026-11-13 02:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-13 08:01 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@0041b69d1736` — **merged** since 2026-11-13T08:01:05Z **Source** — source.main moved to novox/mesh-catalog@32f1566cc879. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `feature/1979-zfs-owns-zfs`: novox/mesh-catalog@0041b69d1736, novox/mesh-delivery@ad7e58091801, novox/mesh-host@96a869063977, novox/mesh-sdk@2895a21e69cd, novox/mesh-tools@df2162e381f5 - composed together: pass — the checker's verdict at the members' heads (13bf070ecb87) **Transitions** - 2026-11-13 02:31 (new) → proposed (announced): novox/mesh-catalog#676's head announced - 2026-11-13 02:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-13 08:01 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

jschoubben added 6 commits 2026-11-13 02:31:19 +00:00

mesh-conditions: the keeper reads zfs's findings (A-32) aa0a472b29

The group's check failed TestEveryControllerKindHasItsHome: the reader zfs's findings are not read by the keeper.

Builds: design 42 zfs-owns-zfs §27, A-32

zfs: the keeper tests make their socket directory in the test's own temporary directory 8ae4fabfbe

The group's check failed TestOnlyRootOpensTheKeepersSocketAndANeedlessKeeperIsTheBusDown and TestAKeeperThatDoesNotAnswerIsWarnedOnce: stat /var/tmp: no such file or directory.

Builds: design 42 zfs-owns-zfs §18, A-37

zfs: the zed-functions file names its notification services on purpose, with its reason 064ebc9b84

The group's check failed TestRulesBus/NoCatalogueManifestNamesAnInstallation: 11 values name an installation (the vendor sites in the package's zed-functions.sh, resources[13]).

Builds: design 42 zfs-owns-zfs §14, A-2

mesh-hand-acts: the whole test dates its warrant from now, inside the 14-day window afa825f902

Issue 1979, blocking: a date-bound test. The warrant dated 2026-10-29 fell out of the listing's 14 days on 2026-11-13, failing every mesh-catalog check.

Builds: design 42 zfs-owns-zfs (the group's check)

zfs: the keeper tests' socket directory is the shortest that works d1a15ced6c

In the test's temporary directory, or /tmp when the socket path would pass 100 characters, so a long TMPDIR cannot fail the bind.

Builds: design 42 zfs-owns-zfs §18, A-37

zfs: findings is a state of the module's state list, not of requires, so the conditions keeper reads it

mesh/delivery merged: source.main moved to novox/mesh-catalog@32f1566cc879

Details

mesh/delivery-group group feature/1979-zfs-owns-zfs merged: every member is merged

Details

mesh/check being carried to 0041b69d1736 on 32f1566cc879 | from 117f933dacf0, mesh-delivery 7221a1e5cd7f, mesh-host 0193949efe9f, mesh-sdk e42b9491c93…

0041b69d17

The validator refused zfs and mesh-conditions: mesh-conditions reads zfs.findings, which zfs had moved to bus state in requires, where the new form has no readers (ADR 0596 section 2). The keeper process's bus.state keeps naming findings. The manifest test holds it.

Builds: design 42 zfs-owns-zfs A-46 (A-32, 26, 27)

mesh-tools commented

2026-11-13 02:31:28 +00:00

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-tools merged commit 32f1566cc8 into main

2026-11-13 08:01:02 +00:00

mesh-tools deleted branch feature/1979-zfs-owns-zfs

2026-11-13 08:01:02 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#676