Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Sergiu Cozma <lssjbrolli@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fix for ERROR: cannot read chunk root
Date: Thu, 7 Nov 2019 08:44:34 +0800
Message-ID: <1e600b1e-f61b-ab7a-85bc-8bd1710c2ea9@gmx.com> (raw)
In-Reply-To: <CAJjG=77Csw5P4q1sPeinoT=y=9Gy=FUr88NK2mJH72OBExnHgQ@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]



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
>>>
>>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent 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
2019-11-07  0:44     ` Qu Wenruo [this message]
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=1e600b1e-f61b-ab7a-85bc-8bd1710c2ea9@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lssjbrolli@gmail.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