Am 2011-05-04 13:51, schrieb cwillu:
that looks very unplausible to me. there is an RAID1 layer beneath btrfs in
our setup and i don't see any errors there.
That doesn't rule out the possibility of corruption when it was
written in the first place, or some similar problem that the raid1
faithfully reproduced on both mirrors. That's not to say that it's
impossible that the problem is in btrfs, just that it's not the only
plausible possibility.
well -- i am doing a backup of all images every night. this process
should work like a simple "scrub" because all data (and its checksumes)
will be read. that's the way i stumbled over this problem!
and the 'nodatasum' option should also ignore csum issues.-- isn't it?
>
No, it only affects writing new checksums; any existing checksums are
still checked.
would it make some sense to remount the volume with checksumming enabled
and run additional tests to find similar suspect blocks to prevent this
kind of suddenly broken files?
martin
--
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
