Re: btrfs check: backref lost, mismatch with its hash -- can't repair

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2018年01月25日 20:29, ^m'e wrote:
> No luck this time:
> 
> # ./btrfs-corrupt-block.static -X /dev/sdb3
> ERROR: Failed to unlink the old file "Manifest": No such file or directory
> extent buffer leak: start 4210688 len 16384
> extent_io.c:607: free_extent_buffer_internal: BUG_ON `eb->flags &
> EXTENT_DIRTY` triggered, value 1
> [0x416a32]
> [0x41720e]
> [0x41725a]
> [0x40a6e1]
> [0x40aee3]
> [0x403245]
> [0x43ba83]
> [0x43bbdf]
> [0x400989]
> Aborted

Checked the dump again, no need to unlink, just remove the offending
item should be good enough.

Branch updated, please check again.

Thanks,
Qu

> 
> On Thu, Jan 25, 2018 at 12:09 PM, Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote:
>> Confirmed same problem as previous root.
>>
>> So branch updated to fix the same problem for root 257.
>>
>> Please try and see if the following error message is gone:
>>
>> ------
>> ERROR: root 257 DIR_ITEM[30039322 4007295565] couldn't find relative
>> INODE_ITEM[0] namelen 0 filename  filetype 0
>> ERROR: root 257 DIR_ITEM[30039322 4007295565] data_len shouldn't be 32907
>> ERROR: root 257 DIR_ITEM[30039322 4007295565] couldn't find relative
>> INODE_ITEM[0] namelen 3 filename  filetype 0
>> ------
>>
>> Thanks,
>> Qu
>>
>>
> 
> 
> 

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux