linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergiu Cozma <lssjbrolli@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fix for ERROR: cannot read chunk root
Date: Wed, 6 Nov 2019 17:52:33 +0200	[thread overview]
Message-ID: <CAJjG=77Csw5P4q1sPeinoT=y=9Gy=FUr88NK2mJH72OBExnHgQ@mail.gmail.com> (raw)
In-Reply-To: <187ab271-f2be-9e96-e73a-0f6f3e97655a@gmx.com>

Hi, thanks for taking the time to help me out with this.

The history is kinda bad, I tried to resize the partition but gparted
failed saying that the the fs has errors and after throwing some
commands found on the internet at it now I'm here :(

Any chance to recover or rebuild the chunk tree?


On Wed, Nov 6, 2019, 13:34 Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>
>
>
> On 2019/11/5 下午11:04, Sergiu Cozma wrote:
> > hi, i need some help to recover a btrfs partition
> > i use btrfs-progs v5.3.1
> >
> > btrfs rescue super-recover https://pastebin.com/mGEp6vjV
> > btrfs inspect-internal dump-super -a https://pastebin.com/S4WrPQm1
> > btrfs inspect-internal dump-tree https://pastebin.com/yX1zUDxa
> >
> > can't mount the partition with
> > BTRFS error (device sdb4): bad tree block start, want 856119312384 have 0
>
> Something wiped your fs on-disk data.
> And the wiped one belongs to one of the most essential tree, chunk tree.
>
> What's the history of the fs?
> It doesn't look like a bug in btrfs, but some external thing wiped it.
>
> Thanks,
> Qu
>
> > [ 2295.237145] BTRFS error (device sdb4): failed to read chunk root
> > [ 2295.301067] BTRFS error (device sdb4): open_ctree failed
> >
>

  reply	other threads:[~2019-11-06 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 15:04 fix for ERROR: cannot read chunk root Sergiu Cozma
2019-11-06 10:48 ` Sergiu Cozma
2019-11-06 11:34 ` Qu Wenruo
2019-11-06 15:52   ` Sergiu Cozma [this message]
2019-11-06 16:21     ` Sergiu Cozma
2019-11-06 22:19       ` Sergiu Cozma
2019-11-07  0:44     ` Qu Wenruo
2019-11-07  7:16       ` Sergiu Cozma
2019-11-10 15:40         ` Sergiu Cozma
2019-11-11  1:46           ` Qu Wenruo

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='CAJjG=77Csw5P4q1sPeinoT=y=9Gy=FUr88NK2mJH72OBExnHgQ@mail.gmail.com' \
    --to=lssjbrolli@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.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).