FreeBSD 15: periodic security run stalls on large filesystem scan

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Nightly security reports arrive late or never complete, reducing operational visibility.

Environment & Reproduction

Appears when periodic jobs scan very large or deeply nested filesystems without exclusions.

Root Cause Analysis

Unbounded traversal and expensive checks exceed maintenance window and contend with production IO.

Quick Triage

Identify hanging subtask, current scan path, and runtime overlap with backup or batch jobs.

Step-by-Step Diagnosis

Profile periodic execution stages and isolate the filesystem regions causing extreme delay.

Solution – Primary Fix

Scope scan targets, add exclusions, and schedule heavy checks in low-traffic windows.

Solution – Alternative Approaches

Offload deep integrity checks to dedicated maintenance hosts or stagger checks by dataset.

Verification & Acceptance Criteria

Periodic jobs complete within window and generated reports include full expected sections.

Rollback Plan

Reinstate prior periodic configuration if scoped checks miss mandatory compliance controls.

Prevention & Hardening

Continuously track job duration and enforce runtime budgets with alert thresholds.

Related Errors & Cross-Refs

Linked with inode-heavy scans, mounted backup snapshots, and antivirus full sweep overlap.

Related tutorial: View the step-by-step tutorial for freebsd-15.

View all freebsd-15 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

periodic.conf man page and FreeBSD system maintenance operational recommendations.