Linux-BTRFS Archive on lore.kernel.org
 help / color / 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: Thu, 7 Nov 2019 00:19:48 +0200
Message-ID: <CAJjG=77gtuw0wMJeL62MJoznekz7dyzCBTvmRTL5WrtzfhQhVA@mail.gmail.com> (raw)
In-Reply-To: <CAJjG=76E8X7h3UR2PDF1RsdRLgeMfwK_cF=OXkE8qBWOmUHfZQ@mail.gmail.com>

additional info: it's a simple partition on a samsung 840evo ssd, no
encryption, no md, no raid
 mount flags rw,relatime,ssd,space_cache,subvolid=5,subvol=/ mounted as /home
and it's pretty old(couple of years) and i'm like 70% sure it was
converted from ext4

On Wed, Nov 6, 2019 at 6:21 PM Sergiu Cozma <lssjbrolli@gmail.com> wrote:
>
> btrfs inspect-internal dump-super -af /dev/sdb4 | grep chunk_root
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
> chunk_root_generation   687369
> chunk_root              856119312384
> chunk_root_level        1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>                backup_chunk_root:      856119312384    gen: 687369     level: 1
>
> if i understand this correctly there is only one copy of the chunk
> root in the whole fs and mine is corrupted?
>
> On Wed, Nov 6, 2019 at 5:52 PM Sergiu Cozma <lssjbrolli@gmail.com> 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 :(
> >
> > 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 index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 15:04 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 [this message]
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 publically 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=77gtuw0wMJeL62MJoznekz7dyzCBTvmRTL5WrtzfhQhVA@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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git