From: Karl-Philipp Richter <richter@richtercloud.de>
To: linux-btrfs@vger.kernel.org
Subject: How to deal with "The chunks in memory can not match the metadata of the fs. Repair failed."?
Date: Mon, 15 Sep 2014 16:59:27 +0200 [thread overview]
Message-ID: <5416FECF.5030709@richtercloud.de> (raw)
Hi together,
I'm currently encountering another issue with `btrfs rescue
chunk-recover`. After some seconds of maximal I/O activity, the program
is idle for some seconds and then prints
The chunks in memory can not match the metadata of the fs. Repair
failed.
Fail to recover the chunk tree.
I don't find any mention of this output except in the source code (this
is as well the only thing $SEARCH_ENGINE points me to). What is the
recommended next step? It would be nice to see the situation (The chunks
in memory can not match the metadata of the fs) or the output mentioned
in `man btrfs rescue`.
Any help is appreciated.
-Kalle
next reply other threads:[~2014-09-15 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:59 Karl-Philipp Richter [this message]
2014-09-16 1:46 ` How to deal with "The chunks in memory can not match the metadata of the fs. Repair failed."? Gui Hecheng
2014-12-18 22:06 ` Karl-Philipp Richter
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=5416FECF.5030709@richtercloud.de \
--to=richter@richtercloud.de \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).