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: Sun, 10 Nov 2019 17:40:02 +0200 [thread overview]
Message-ID: <CAJjG=74O4oMPpDkj2Ue2b+scnb6AM8Bvh_e3ZGQr2_gTEVSUuQ@mail.gmail.com> (raw)
In-Reply-To: <CAJjG=74LUiRLbJiJ_BwgirqkA=i72t0GfJB0Masgkg0NHY0ozA@mail.gmail.com>
root 856153161728
chunk_root 856119312384
Aren't those nr too high for a 416GB partition?
On Thu, Nov 7, 2019 at 9:16 AM Sergiu Cozma <lssjbrolli@gmail.com> wrote:
>
> Well nothing to lose now so if you come up with any exotic ideas you
> wanna try please let me know, I will keep the partition for the next
> couple of days.
>
> Thank you for your time.
>
> On Thu, Nov 7, 2019 at 2:44 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> >
> >
> >
> > On 2019/11/6 下午11:52, Sergiu Cozma wrote:
> > > 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 :(
> >
> > Not sure how gparted handle resize, but I guess it should use
> > btrfs-progs to do the resize?
> >
> > >
> > > Any chance to recover or rebuild the chunk tree?
> >
> > I don't think so. Since it's wiped, there is no guarantee that only
> > chunk tree is wiped.
> >
> > THanks,
> > Qu
> >
> >
> > >
> > >
> > > 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
> > >>>
> > >>
> >
next prev parent reply other threads:[~2019-11-10 15:40 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
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 [this message]
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=74O4oMPpDkj2Ue2b+scnb6AM8Bvh_e3ZGQr2_gTEVSUuQ@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).