On 2018年06月30日 10:44, Marc MERLIN wrote:
> Well, there goes that. After about 18H:
> ERROR: extent[156909494272, 55320576] referencer count mismatch (root: 21872,
> owner: 374857, offset: 235175936) wanted: 1, have: 1452
> backref.c:466: __add_missing_keys: Assertion `ref->root_id` failed, value 0
> btrfs(+0x3a232)[0x56091704f232]
> btrfs(+0x3ab46)[0x56091704fb46]
> btrfs(+0x3b9f5)[0x5609170509f5]
> btrfs(btrfs_find_all_roots+0x9)[0x560917050a45]
> btrfs(+0x572ff)[0x56091706c2ff]
> btrfs(+0x60b13)[0x560917075b13]
> btrfs(cmd_check+0x2634)[0x56091707d431]
> btrfs(main+0x88)[0x560917027260]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f93aa508561]
> btrfs(_start+0x2a)[0x560917026dfa]
> Aborted
I think that's the root cause.
Some invalid extent tree backref or bad tree block blow up backref code.
All previous error message may be garbage unless you're using Su's
latest branch, as lowmem mode tends to report false alerts on refrencer
count mismatch.
But the last abort looks pretty possible to be the culprit.
Would you try to dump the extent tree?
# btrfs inspect dump-tree -t extent <device> | grep -A50 156909494272
It should help us locate the culprit and hopefully get some chance to
fix it.
Thanks,
Qu
>
> That's https://github.com/Damenly/btrfs-progs.git
>
> Whoops, I didn't use the tmp1 branch, let me try again with that and
> report back, although the problem above is still going to be there since
> I think the only difference will be this, correct?
> https://github.com/Damenly/btrfs-progs/commit/b5851513a12237b3e19a3e71f3ad00b966d25b3a
>
> Marc
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
