Re: read time tree block corruption detected

[Qu Wenruo <quwenruo.btrfs@gmx.com>]

On 2020/1/17 下午3:54, Peter Luladjiev wrote:
> Should I run with repair flag?

Please only run --repair with the fs unmounted.

Thanks,
Qu

>
> On Fri, 17 Jan 2020 at 09:51, Peter Luladjiev <luladjiev@gmail.com> wrote:
>>
>> Here is the output:
>>
>> btrfs check --force --mode lowmem /dev/mapper/system-root
>>
>> Opening filesystem to check...
>> WARNING: filesystem mounted, continuing because of --force
>> Checking filesystem on /dev/mapper/system-root
>> UUID: 9639a3e6-cd08-4270-b4d1-d2946d2b8d2e
>> [1/7] checking root items
>> [2/7] checking extents
>> [3/7] checking free space cache
>> btrfs: space cache generation (539645) does not match inode (539641)
>> failed to load free space cache for block group 22020096
>> btrfs: space cache generation (539645) does not match inode (539641)
>> failed to load free space cache for block group 1095761920
>> btrfs: space cache generation (539643) does not match inode (539640)
>> failed to load free space cache for block group 102161711104
>> [4/7] checking fs roots
>> [5/7] checking only csums items (without verifying data)
>> [6/7] checking root refs done with fs roots in lowmem mode, skipping
>> [7/7] checking quota groups skipped (not enabled on this FS)
>> found 53501751296 bytes used, no error found
>> total csum bytes: 43476196
>> total tree bytes: 1552203776
>> total fs tree bytes: 1422196736
>> total extent tree bytes: 70172672
>> btree space waste bytes: 276902557
>> file data blocks allocated: 331882188800
>>  referenced 105424904192
>>
>> On Fri, 17 Jan 2020 at 09:34, Nikolay Borisov <nborisov@suse.com> wrote:
>>>
>>>
>>>
>>> On 16.01.20 г. 18:53 ч., Peter Luladjiev wrote:
>>>> Hello, thanks for helping, here is the output:
>>>>
>>>> btrfs check --force /dev/mapper/system-root
>>>>
>>>> Opening filesystem to check...
>>>> WARNING: filesystem mounted, continuing because of --force
>>>> Checking filesystem on /dev/mapper/system-root
>>>> UUID: 9639a3e6-cd08-4270-b4d1-d2946d2b8d2e
>>>> [1/7] checking root items
>>>> [2/7] checking extents
>>>> ref mismatch on [1497018368 4096] extent item 72057183177116417, found 1
>>>> incorrect local backref count on 1497022464 parent 51611369472 owner 0
>>>> offset 0 found 1 wanted 3087007745 back 0x564582174c70
>>>> backpointer mismatch on [1497022464 4096]
>>>> ERROR: errors found in extent allocation tree or chunk allocation
>>>> [3/7] checking free space cache
>>>> [4/7] checking fs roots
>>>> [5/7] checking only csums items (without verifying data)
>>>> [6/7] checking root refs
>>>> [7/7] checking quota groups skipped (not enabled on this FS)
>>>> found 53532647424 bytes used, error(s) found
>>>> total csum bytes: 43476204
>>>> total tree bytes: 1551368192
>>>> total fs tree bytes: 1421295616
>>>> total extent tree bytes: 70238208
>>>> btree space waste bytes: 276638054
>>>> file data blocks allocated: 331679563776
>>>>  referenced 105423634432
>>>>
>>>
>>>
>>> Right so it seems this the only error. Just to be sure run btrfs check
>>> --mode lowmem  since it provides more readable output. If this is the
>>> only error in the filesystem then btrfs check --repair --mode lowmem
>>> should be able to fix it.