linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karl-Philipp Richter <richter@richtercloud.de>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: How to deal with "The chunks in memory can not match the metadata of the fs. Repair failed."?
Date: Thu, 18 Dec 2014 23:06:08 +0100	[thread overview]
Message-ID: <54934FD0.7080505@richtercloud.de> (raw)
In-Reply-To: <1410831965.14842.4.camel@localhost.localdomain>

Hi,
Just to give you a really late feedback on this: I got it fixed with
btrfs-progs 3.17.3n on Linux 3.17.6, i.e. `btrfs rescue chunk-recover`
just did the job. Thanks for your advice.

-Kalle

Am 09/16/2014 um 03:46 AM schrieb Gui Hecheng:
> On Mon, 2014-09-15 at 16:59 +0200, Karl-Philipp Richter wrote:
>> 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
> 
> Hi Kalle,
> If you are encountering the above msg, it means the chunk tree has some
> inconsistent stuff with other trees like device tree & extent tree.
> You can specify the '-v' option for chunk-recover to see more details.
> 
> And also, the btrfs check cmd may tell more about the story.
> 
> Thanks,
> Gui
> 
> 
>> --
>> 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
> 
> 
> --
> 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
> 

      reply	other threads:[~2014-12-18 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 14:59 How to deal with "The chunks in memory can not match the metadata of the fs. Repair failed."? Karl-Philipp Richter
2014-09-16  1:46 ` Gui Hecheng
2014-12-18 22:06   ` Karl-Philipp Richter [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=54934FD0.7080505@richtercloud.de \
    --to=richter@richtercloud.de \
    --cc=guihc.fnst@cn.fujitsu.com \
    --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).