I have a btrfs disk that suffered some damage from hardware failure and spits i/o errors when copying certain files. I ran btrfs scrub, and when it reported csum errors I offlined it and did a
btrfs check --check-data-csum and it returned several dozen of the following lines:
mirror 0 bytenr 549766098944 csum 1874004453 expected csum 2335064354
As far as I know, using
--backup has a good chance to fix this problem, and would be the first step to take in repairing the file system. However, this was my virtual disk storage for qemu, and I'm worried that the internal congruity of the virtual disks (especially the windows one) will be harmed if I do this.
The btrfs manpage mentions an
--init-csum-tree flag alongside other dangerous commands. Is this a good excuse to use this, or do I have other options?
CentOS Linux 7, kernel 3.10.0-514.26.2.el7.x86_64
btrfs-progs version 4.4.1 release 1.el7
Disk is a WD red 6TB (5.5TiB) WD60EFRX, one 5.5TiB partition
Virtual disks are in .qcow2 format