Now the problems are all located:
For file "2f3f379b2a3d7499471edb74869efe-1948311.d", it's the problem of
its DIR_ITEM has wrong type:
------
item 14 key (57648595 DIR_ITEM 3363354030) itemoff 3053 itemsize 70
location key (57923894 INODE_ITEM 0) type DIR_ITEM.33
^^^^^^^^^^^
------
There is unexpected type DIR_ITEM and a special number 33 here.
Despite that, the file is completely fine.
For file "454bf066ddfbf42e0f3b77ea71c82f-878732.o"
The problem is its namelen.
------
item 13 key (57648595 DIR_ITEM 3331247447) itemoff 3123 itemsize 69
location key (58472210 INODE_ITEM 0) type FILE
transid 89418 data_len 0 name_len 8231
^^^^ Insane
name: 454bf066ddfbf42e0f3b77ea71c82f-878732.oq
------
Despite that, it should be fine.
I'm not 100% sure if repair can really handle it well.
But I could craft a temporary fix based on btrfs-corrupt-block (I know
the name is scary).
And you may need to compile btrfs-progs with my patch.
The only remaining thing I need is the subvolume id which contains the
corrupted files.
Since there is no other hit, I assume it's root subvolume (5), but I
still need the extra confirm since the fix will be hard-coded.
Thanks,
Qu
Attachment:
signature.asc
Description: OpenPGP digital signature
