On Apr 24, 2014, at 8:43 PM, Andreas Reis <andreas.r...@gmail.com> wrote:
> Andreas Reis <andreas.reis <at> gmail.com> writes: > >> Turns out that when I try to run any binary from the restored >> partition (via LiveCD), *every* *single* *one* fails with this >> remarkably expressive error. If I manually replace one with a >> fresh download, I get a SIGBUS crash instead. > > Alright, there are corrupt text files too, after all. As well as a > handful or non-corrupted binaries. > > Always the same type of btrfs error message though. Interestingly, > the false csum reported stays exactly the same: 2566472073. Also, > btrfs check --init-csum-tree fails with a plethora of backref > errors. That command obliterates the csum tree. csums are not recomputed for already written files. Anytime you read an existing file, e.g. merely copy it, you'll get a long pile of csum errors because there's missing csums. btrfs check itself is benign, but the options --init* and --repair have been fairly vertical fixes for specific problems and can make others worse; although that experience is largely based on older progs. I'm not sure yet how well 3.14 is repairing, and haven't looked at the changelog to see if btrfsck has been significantly updated in it. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
