2021-11-30 15:00:48 +00:00
|
|
|
Auto-repair on read
|
|
|
|
|
===================
|
|
|
|
|
|
2022-12-07 20:00:25 +00:00
|
|
|
Data or metadata that are found to be damaged (e.g. because the checksum does
|
2022-12-14 01:56:16 +00:00
|
|
|
not match) at the time they're read from a device can be salvaged in case the
|
2021-12-09 19:46:42 +00:00
|
|
|
filesystem has another valid copy when using block group profile with redundancy
|
2022-12-14 01:56:16 +00:00
|
|
|
(DUP, RAID1-like, RAID5/6). The correct data are returned to the user application
|
|
|
|
|
and the damaged copy is replaced by it. When this happen a message is emitted
|
|
|
|
|
to the system log.
|
|
|
|
|
|
|
|
|
|
If there are more copies of data and one of them is damaged but not read by
|
|
|
|
|
user application then this is not detected. To verify all data and metadata
|
|
|
|
|
copies there's :doc:`scrub<Scrub>` that needs to be started manually, automatic
|
|
|
|
|
repairs happens in that case.
|
