On Thu, Nov 07, 2013 at 10:56:10PM -0700, Chris Murphy wrote: > What's the kernel and btrfs progs version? > > I wish the dmesg errors were more explicit about the nature of checksum > errors: do the two metadata checksums mismatch each other (one of them > matches with data), or the metadata checksums match each other but mismatch > with data?
If there's two copies, and one fails the checksum and the other passes, then there will be a note following the failure that it read the other checksum and succeeded, and repaired the problem. > Hopefully I'm mistaken, but it looks in this case that the data is actually > corrupt, not the metadata. In which case repair would only be possible for > raid1 or raid10 data profiles. > > Why the corruption occurred depends on kernel and btrfs-progs versions, and > what you were doing prior to the corruption so dmesg prior to the corruption > would be needed and also when trying to mount with the recovery option so it > might be worth: > > dmesg > [note the last time entry] > dmesg -n7 > btrfs mount -o recovery <dev> <mp> > dmesg > > report results since the previously noted last time entry > > > 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 -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- For months now, we have been making triumphant retreats --- before a demoralised enemy who is advancing in utter disorder.
signature.asc
Description: Digital signature
