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 08:59:17 +0800 [thread overview]
Message-ID: <95a8eb10-8fa7-c1c7-13c3-e4fd194fd76a@gmx.com> (raw)
In-Reply-To: <CAAxOLF8KgC=_LoaEaKft2Q7gUhKL3Fp8OLizbnnA9v4h_cSprQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3117 bytes --]
On 2018年01月25日 03:00, ^m'e wrote:
> The complete check:
>
> Checking filesystem on /dev/sdb3
> UUID: de1723e2-150c-4448-bb36-be14d7d96093
> ERROR: extent[64368619520, 524288] referencer count mismatch (root:
> 257, owner: 7804556, offset: 212992) wanted: 1, have: 0
> ERROR: data extent[1862352896 425984] backref lost
> ERROR: data extent[1886453760 479232] backref lost
> ERROR: data extent[1902219264 524288] backref lost
> ERROR: data extent[1817378816 151552] backref lost
> ERROR: data extent[1799688192 57344] backref lost
> ERROR: data extent[1830277120 258048] backref lost
> ERROR: data extent[2558107648 1368064] backref lost
Well, a little surprised to know that --repair doesn't repair it.
I'll fix them after all other problems are fixed.
> ERROR: errors found in extent allocation tree or chunk allocation
> cache and super generation don't match, space cache will be invalidated
> 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
OK, another root, other than the root I'm repairing.
So the corruption seems to happen in multiple snapshots.
Anyway, I could fix it using the same code, just changing the root objectid.
At least, the fix in the offending DIR_ITEM is working.
Just a few more roots needs to be fixed.
> ERROR: root 257 DIR_ITEM[30039322 4007295565] couldn't find relative
> INODE_ITEM[0] namelen 3 filename filetype 0
> ERROR: root 258 EXTENT_DATA[1119172 1966080] prealloc shouldn't have datasum
> ERROR: root 1327 EXTENT_DATA[60710 18219008] prealloc shouldn't have datasum
> ERROR: root 1331 EXTENT_DATA[60710 18219008] prealloc shouldn't have datasum
> ERROR: root 1333 EXTENT_DATA[60710 18219008] prealloc shouldn't have datasum
> ERROR: root 1362 EXTENT_DATA[1119172 1966080] prealloc shouldn't have datasum
> ERROR: root 1366 EXTENT_DATA[1119172 1966080] prealloc shouldn't have datasum
> ERROR: root 1382 EXTENT_DATA[1119172 1966080] prealloc shouldn't have datasum
Not a big problem, so handle it later.
> ERROR: root 1385 DIR_ITEM[30039322 2438219243] couldn't find relative
> INODE_ITEM[0] namelen 12 filename metadata.xml filetype 1
> ERROR: root 1385 DIR INODE [30039322] size(152) not equal to 136
> ERROR: root 1385 INODE REF[30039324 30039322] and DIR_ITEM[30039322
> 2438219243] mismatch namelen 12 filename metadata.xml filetype 1
And I forgot this one.
But this is pretty simple, I'll focus on previous problems and handle it
later.
Thanks,
Qu
> found 104348008448 bytes used err is -5
> total csum bytes: 99534904
> total tree bytes: 3204612096
> total fs tree bytes: 2984034304
> total extent tree bytes: 87818240
> btree space waste bytes: 778261104
> file data blocks allocated: 242964852736
> referenced 198454632448
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2018-01-25 0:59 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
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 [this message]
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=95a8eb10-8fa7-c1c7-13c3-e4fd194fd76a@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).