translator
987
edits
Difference between revisions of "Btrfs"
m
Upercase title
m (Upercase title) |
m (Upercase title) |
||
| Line 227: | Line 227: | ||
Every now and then it is advisable to look for such things. And fix it right away! | Every now and then it is advisable to look for such things. And fix it right away! | ||
==== | ==== Check & repair on the fly ==== | ||
Every time btrfs reads a file, it checks the corresponding checksums. When btrfs is in RAID 0 and detects a 'damaged' file, it only can tell you that the file is damaged. You may delete it, or replace it from your backup. | Every time btrfs reads a file, it checks the corresponding checksums. When btrfs is in RAID 0 and detects a 'damaged' file, it only can tell you that the file is damaged. You may delete it, or replace it from your backup. | ||
When running in RAID 1 btrfs has 2 copies of every file. So if one file seems to be damaged, btrfs will read the other copy. If this other copy is ok, btrfs will automatically create another good copy of the file, and then afterwards delete the defect copy. You won't even notice this ''''automatic' repair.''' | When running in RAID 1 btrfs has 2 copies of every file. So if one file seems to be damaged, btrfs will read the other copy. If this other copy is ok, btrfs will automatically create another good copy of the file, and then afterwards delete the defect copy. You won't even notice this ''''automatic' repair.''' | ||
==== | ==== Full check ==== | ||
Sometimes you may want to check ALL files, and to get a report of defects, because: | Sometimes you may want to check ALL files, and to get a report of defects, because: | ||
* Some files are read very seldom, and you don't want "bitrott" | * Some files are read very seldom, and you don't want "bitrott" | ||