From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "^m'e" <marcoep@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs check: backref lost, mismatch with its hash -- can't repair
Date: Thu, 25 Jan 2018 20:37:18 +0800 [thread overview]
Message-ID: <80321b99-a89c-fadf-8f1a-26ed8f598a66@gmx.com> (raw)
In-Reply-To: <CAAxOLF8wt98KCONdEJXMvUuzxeB5_GwigGhCzEE6hSpmurXRNw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
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@gmx.com> 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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2018-01-25 12:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:11 btrfs check: backref lost, mismatch with its hash -- can't repair ^m'e
2018-01-22 14:38 ` Qu Wenruo
2018-01-22 15:04 ` ^m'e
2018-01-24 8:49 ` Qu Wenruo
2018-01-24 9:18 ` Foo Bar
2018-01-24 10:14 ` Qu Wenruo
2018-01-24 11:57 ` ^m'e
2018-01-24 12:39 ` Qu Wenruo
2018-01-24 14:47 ` ^m'e
2018-01-24 19:00 ` ^m'e
2018-01-24 20:41 ` ^m'e
2018-01-25 0:59 ` Qu Wenruo
2018-01-25 11:54 ` ^m'e
2018-01-25 12:09 ` Qu Wenruo
2018-01-25 12:29 ` ^m'e
2018-01-25 12:37 ` Qu Wenruo [this message]
2018-01-25 16:40 ` ^m'e
2018-01-25 23:30 ` Qu Wenruo
2018-01-26 11:19 ` ^m'e
2018-01-26 12:16 ` Qu Wenruo
2018-01-26 15:15 ` ^m'e
2018-01-29 1:34 ` Qu Wenruo
2018-01-29 13:58 ` ^m'e
2018-01-29 14:04 ` Qu Wenruo
2018-01-29 14:49 ` ^m'e
2018-01-29 15:08 ` ^m'e
2018-01-29 15:10 ` Qu Wenruo
2018-01-29 15:09 ` Qu Wenruo
2018-01-29 18:16 ` ^m'e
2018-01-30 1:24 ` Qu Wenruo
2018-01-30 20:14 ` Foo Bar
2018-01-25 0:59 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80321b99-a89c-fadf-8f1a-26ed8f598a66@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcoep@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).