On Sun, Feb 15, 2015 at 5:06 PM, Tim DeNike <[email protected]> wrote: > Long story short.. Ive been having problems with random files getting > uncorrectable CRC errors on a 23TB filesystem.. RAID6 on an LSI card.
This is LSI hardware RAID6? Or Btrfs raid6 with an LSI HBA? If you can still mount -o ro, what do you get for btrfs fi df <mp> The former setup won't have copies for everything, only for inline data if metadata profile is dup. So there's not much point to init-csum-tree, there is corruption somewhere and reiniting the csum tree just masks that problem (probably temporarily). I just took a new btrfs volume created with kernel-3.10.0-123.el7.x86_64 and btrfs-progs v3.12 from CentOS 7. Nuked the csum tree with --repair --init-csum-tree, which actually somehow incidentally caused damage to the extent tree. The csum tree is empty and anything not stored inline (metadata) has csum errors.Then I upgraded to kernel-3.19.0-1.el7.elrepo.x86_64 and btrfs-progs-3.18.2, and did another --repair --init-csum-tree, and now everything is fixed. No errors and no crash. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
