From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Marc MERLIN <marc@merlins.org>, Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.cz>
Subject: Re: btrfs check: add_missing_dir_index: BUG_ON `ret` triggered, value -17
Date: Fri, 17 Nov 2017 13:17:19 +0800 [thread overview]
Message-ID: <3e4de2ce-28c8-23c0-c25d-70659a378865@gmx.com> (raw)
In-Reply-To: <20171117022615.GO10969@merlins.org>
[-- Attachment #1.1: Type: text/plain, Size: 2355 bytes --]
On 2017年11月17日 10:26, Marc MERLIN wrote:
> Howdy,
>
> Up to date git pull from btrfs-progs:
>
> gargamel:~# btrfs check --repair /dev/mapper/raid0d1
> enabling repair mode
> Checking filesystem on /dev/mapper/raid0d1
> UUID: 01334b81-c0db-4e80-92e4-cac4da867651
> checking extents
> corrupt extent record: key 203003699200 168 40960
> corrupt extent record: key 203003764736 168 172032
> ref mismatch on [203003699200 40960] extent item 0, found 1
> Data backref 203003699200 root 258 owner 1933897829 offset 0 num_refs 0 not found in extent tree
> Incorrect local backref count on 203003699200 root 258 owner 1933897829 offset 0 found 1 wanted 0 back 0x5596988c2130
> backpointer mismatch on [203003699200 40960]
> repair deleting extent record: key 203003699200 168 40960
> adding new data backref on 203003699200 root 258 owner 1933897829 offset 0 found 1
> Repaired extent references for 203003699200
> Data backref 203003764736 root 258 owner 1932315368 offset 0 num_refs 0 not found in extent tree
> Incorrect local backref count on 203003764736 root 258 owner 1932315368 offset 0 found 1 wanted 0 back 0x5596dde358f0
> backpointer mismatch on [203003764736 172032]
> repair deleting extent record: key 203003764736 168 172032
> adding new data backref on 203003764736 root 258 owner 1932315368 offset 0 found 1
> Repaired extent references for 203003764736
> Fixed 0 roots.
> checking free space cache
> cache and super generation don't match, space cache will be invalidated
> checking fs roots
> invalid location in dir item 0
> Deleting bad dir index [1919785864,96,1958] root 258
> Deleting bad dir index [1919785864,96,1957] root 258
> repairing missing dir index item for inode 1919805647
> cmds-check.c:2614: add_missing_dir_index: BUG_ON `ret` triggered, value -17
-EEXIST. Btrfs check --repair is trying to re-insert some key which
exists already.
Would you please provide the output of "btrfs-debug-tree -t 258 | grep
1919805647" to help the debugging?
Thanks,
Qu
> btrfs(+0x52207)[0x55966a6fa207]
> btrfs(+0x5225a)[0x55966a6fa25a]
> btrfs(+0x5cef3)[0x55966a704ef3]
> btrfs(cmd_check+0x2e10)[0x55966a70ea35]
> btrfs(main+0x85)[0x55966a6b9dc3]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f794aadf2b1]
> btrfs(_start+0x2a)[0x55966a6b993a]
> Aborted
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-11-17 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 2:26 btrfs check: add_missing_dir_index: BUG_ON `ret` triggered, value -17 Marc MERLIN
2017-11-17 5:17 ` Qu Wenruo [this message]
2017-11-17 6:17 ` Marc MERLIN
2017-11-17 7:30 ` Marc MERLIN
2017-11-17 8:12 ` Qu Wenruo
2017-11-17 15:50 ` Marc MERLIN
2017-11-18 0:16 ` Qu Wenruo
2017-11-18 16:34 ` Marc MERLIN
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=3e4de2ce-28c8-23c0-c25d-70659a378865@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.com \
--cc=marc@merlins.org \
/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