jschoubben bb96fbbb3c zfs: the scheduled run names its minutes, so its timer starts (issue 1979) ...

The node-engine writes a cron step (*/15) as a calendar systemd refuses, so
zfs-mesh-scrub.timer never started and the pool had no scrub schedule. A list
of minutes is written as *-*-* *:0,15,30,45:00, which systemd takes.

Builds: design 42 zfs-owns-zfs §18. Tests: 1979/AC1.

2026-11-12 23:07:55 +01:00

..

testdata

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

datasets.go

Add the zfs module, so the mesh can see the home server's pools and snapshot a dataset

2026-10-09 00:11:31 +02:00

events.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

follow.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

health_test.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

health.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

helpers_test.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

io.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

machine.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

main.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

manifest_test.go

zfs: the scheduled run names its minutes, so its timer starts (issue 1979)

2026-11-12 23:07:55 +01:00

parse_test.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

pools.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

properties.go

Add the zfs module, so the mesh can see the home server's pools and snapshot a dataset

2026-10-09 00:11:31 +02:00

review_test.go

Keep three timeout tests' upper bounds well under the production timeouts, so a timeout that falls back to production still fails (issue 1814, review round 3)

2026-11-01 17:26:58 +01:00

schedule.go

Keep the scheduled run's served slot in a folder of root's alone, written never through a link

2026-10-09 01:55:54 +02:00

scrub.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

scrubrun_test.go

Keep the scheduled run's served slot in a folder of root's alone, written never through a link

2026-10-09 01:55:54 +02:00

scrubschedule_test.go

Run the scrub schedule as a scheduled process, never pause a scrub, and keep the pool's name the only setting in a unit

2026-10-09 01:40:02 +02:00

snapshot_test.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

snapshot.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

templates_test.go

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

tools.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00

watch.go

Make the zfs module safe to put on the home server, and give it the pool's scrub schedule

2026-10-09 01:17:34 +02:00