On 2018/12/17 下午8:44, Олег Власов wrote:
> [1/7] checking root items
> [2/7] checking extents
> [3/7] checking free space cache
> [4/7] checking fs roots
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 1741 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2308 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2309 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2310 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2314 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2315 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2342 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2343 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2344 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2345 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2350 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2351 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2400 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2401 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2402 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2403 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2404 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2405 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2406 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2407 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2408 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> ERROR: DIR_ITEM[2531 651003133] name libLLVMAnalysis.so.Ѕ= namelen 24
> filetype 1 mismatch with its hash, wanted 651003133 have 3033451023
> root 2409 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2410 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item
> root 2411 inode 2531 errors 10, odd dir item
> unresolved ref dir 2531 index 0 namelen 24 name libLLVMAnalysis.so.Ѕ=
> filetype 1 errors 6, no dir index, no inode ref
> unresolved ref dir 2531 index 17409 namelen 24 name
> libLLVMAnalysis.so.3.8.0 filetype 1 errors 1, no dir item

So no extent tree problems, all DIR_ITEMS.

It's OK for you to use the following branch, and execute "btrfs check
--repair" to fix the fs:
https://github.com/adam900710/btrfs-progs/tree/check-next

Please note that, current upstream btrfs-progs won't fix it, only that
branch contains the fixing commits.

Thanks,
Qu
> ERROR: errors found in fs roots
> Opening filesystem to check...
> Checking filesystem on /dev/sda5
> UUID: cbc46449-fb64-4a9a-965b-b58646e9f82a
> found 280200617984 bytes used, error(s) found
> total csum bytes: 267811940
> total tree bytes: 2448752640
> total fs tree bytes: 2011480064
> total extent tree bytes: 118505472
> btree space waste bytes: 428923543
> file data blocks allocated: 1238443962368
>  referenced 323581739008
> 
> 
> ср, 12 дек. 2018 г. в 16:52, Qu Wenruo <quwenruo.bt...@gmx.com>:
>>
>>
>>
>> On 2018/12/12 下午9:51, Олег Власов wrote:
>>> Could you guide me ?
>>> What should I do after compile latest btrfs-progs?
>>
>> "btrfs check --readonly <device>" and paste the output.
>>
>> Thanks,
>> Qu
>>
>>>
>>> ср, 12 дек. 2018 г., 16:47 Qu Wenruo quwenruo.bt...@gmx.com
>>> <mailto:quwenruo.bt...@gmx.com>:
>>>
>>>
>>>
>>>     On 2018/12/12 下午9:36, Олег Власов wrote:
>>>     > if there any way to remove that item?
>>>
>>>     IIRC kernel can't remove it since the hash doesn't match, kernel won't
>>>     be able to delete it.
>>>
>>>     btrfs-progs check-next branch can handle it, but you need to ensure
>>>     there is no other bugs.
>>>
>>>     So, you still need to compile the latest btrfs-progs and then the
>>>     check-next branch.
>>>
>>>     Thanks,
>>>     Qu
>>>
>>>     > the file that belong to it is useless for me but it preventing to
>>>     > mount filsystem in higher kernel versions
>>>     > ср, 12 дек. 2018 г. в 16:26, Qu Wenruo <quwenruo.bt...@gmx.com
>>>     <mailto:quwenruo.bt...@gmx.com>>:
>>>     >>
>>>     >>
>>>     >>
>>>     >> On 2018/12/12 下午9:00, Nikolay Borisov wrote:
>>>     >>>
>>>     >>>
>>>     >>> On 12.12.18 г. 14:44 ч., Олег Власов wrote:
>>>     >>>> Hello
>>>     >>>> If anyone could help with with "name hash mismatch" error at btrfs.
>>>     >>>> full error is
>>>     >>>> "BTRFS critical (device sda5): corrupt leaf: root=2234
>>>     >>>> block=244700761008 slot 136 ino=2531, name hash mismatch with key,
>>>     >>>> have 0x000000000026cd84d"
>>>     >>>> so i could not access one file neither to remove it.
>>>     >>>>
>>>     >>>> uname -a
>>>     >>>> Linux linux-wwqj 4.12.14-lp150.12.16-default #1 SMP Tue Aug 14
>>>     >>>> 17:51:27 UTC 2018 (28574e6) x86_64 x86_64 x86_64 GNU/Linux
>>>     >>>> btrfs --version
>>>     >>>> btrfs-progs v4.15
>>>     >>>
>>>     >>> First I'd suggest to update to the latest btrfs progs. Then just run
>>>     >>> btrfs check --readonly --mode lowmem /path/to/device  and paste the
>>>     >>> output. This won't do any changes to your filesystem but will give a
>>>     >>> better idea of what the corruption might be.
>>>     >>
>>>     >> Yep, that's pretty much recommended.
>>>     >>
>>>     >> On the other hand this kernel warning message just means exactly
>>>     what it
>>>     >> says.
>>>     >> One of your DIR_ITEM has incorrect hash.
>>>     >>
>>>     >> IIRC this is an old bug in kernel, not sure when it get fixed but it
>>>     >> should definitely get fixed now.
>>>     >>
>>>     >> If btrfs check --readonly shows *NO OTHER* bug, I have the check-next
>>>     >> branch which could fix it.
>>>     >>
>>>     >> But please keep in mind, don't run btrfs check --repair right now.
>>>     >>
>>>     >> Thanks,
>>>     >> Qu
>>>     >>
>>>     >>>
>>>     >>>>
>>>     >>>> tnx in advance
>>>     >>>>
>>>
>>

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to