I've been trying to understand where some of these numbers come from.
On 05/05/2015 01:06 PM, Perry Gilfillan wrote:
btrfs-image throws a different error,
bytenr mismatch, want=27198603952128, have=13057557201204318535,
where the 'have' seems to be pointing some where out past Pluto!
[root@lightmyfire btrfs-progs-unstable]# ./btrfs-image /dev/sdf5
~/text.txt
parent transid verify failed on 27198602870784 wanted 291859 found 291431
parent transid verify failed on 27198602870784 wanted 291859 found 291431
checksum verify failed on 27198602870784 found C273E746 wanted 26905AF0
parent transid verify failed on 27198602870784 wanted 291859 found 291431
Ignoring transid failure
parent transid verify failed on 27198603952128 wanted 291431 found 291859
parent transid verify failed on 27198603952128 wanted 291431 found 291859
checksum verify failed on 27198603952128 found BC5A7A89 wanted 90B199E8
checksum verify failed on 27198603952128 found BC5A7A89 wanted 90B199E8
bytenr mismatch, want=27198603952128, have=13057557201204318535
Couldn't read chunk tree
Open ctree failed
create failed (Success)
The generation numbers are easy enough. If incremented every 30
seconds, they represent about 100 days of activity.
The other numbers (27198602870784) are leaf nodes in the tree? When the
'bytenr mismatch' error shows up, how would I find the cause and try to
patch it manually?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
