btrfs scrub only covers /mnt/external #124
Labels
No labels
audit-work
bug
docs
general-admin
major-upgrade
needs-vps-sync
new-service
on-hold
outside-work
post-podman
renovate
upstream
vps
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mysticalsoap/docker#124
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
btrfs-scrub@has exactly one timer instance:mnt-external. The LUKS root filesystem — all of/opt/docker, every app database, the restic repo's source data — and/mnt/support(btrfs, nvme) are never scrubbed. Checksums are only verified on read, so cold data can sit corrupt until the day a restore needs it.btrfs-scrub@-.timer(root fs) andbtrfs-scrub@mnt-support.timersmart.prom) so scrub errors and missed runs alert; a scrub that finds errors but tells no one is barely better than none/mnt/disk1(ext4, mergerfs member) has no checksumming at all — accepted for replaceable media, SMART covers the drive itself. Worth revisiting only if the pool grows (snapraid is the usual companion at 3+ data disks).