![]() |
![]()
| ![]() |
![]()
NAME
SYNOPSIS
DESCRIPTIONBegins a scrub or resumes a paused scrub. The scrub examines all
data in the specified pools to verify that it checksums correctly. For
replicated (mirror, raidz, or draid) devices, ZFS automatically repairs any
damage discovered during the scrub. The Scrubbing and resilvering are very similar operations. The difference is that resilvering only examines data that ZFS knows to be out of date (for example, when attaching a new device to a mirror or replacing an existing device), whereas scrubbing examines all data to discover silent errors due to hardware faults or disk failure. When scrubbing a pool with encrypted filesystems the keys do not
need to be loaded. However, if the keys are not loaded and an unrepairable
checksum error is detected the file name cannot be included in the
Because scrubbing and resilvering are I/O-intensive operations, ZFS only allows one at a time. A scrub is split into two parts: metadata scanning and block scrubbing. The metadata scanning sorts blocks into large sequential ranges which can then be read much more efficiently from disk when issuing the scrub I/O. If a scrub is paused, the Note that, due to changes in pool data on a live system, it is possible for scrubs to progress slightly beyond 100% completion. During this period, no completion time estimate will be provided. OPTIONS
EXAMPLESExample 1Status of pool with ongoing scrub: # Where metadata which references 403M of file data has been scanned at 100M/s, and 68.4M of that file data has been scrubbed sequentially at 10.0M/s. PERIODIC SCRUBOn machines using systemd, scrub timers can be enabled on per-pool
basis.
SEE ALSOsystemd.timer(5), zpool-iostat(8), zpool-resilver(8), zpool-status(8)
|