From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Yegor Yegorov <gochkin@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Help needed to recover from partition resize/move
Date: Sun, 26 Apr 2020 08:58:39 +0300 [thread overview]
Message-ID: <88488595-8392-c6e2-2784-84607c233d84@gmail.com> (raw)
In-Reply-To: <CAJCQCtSdyP_SspJGwitWSOM1mvT-_ykXGq_azk=R+jqCZ+V4Yw@mail.gmail.com>
26.04.2020 03:56, Chris Murphy пишет:
> On Sat, Apr 25, 2020 at 3:55 PM Yegor Yegorov <gochkin@gmail.com> wrote:
>>
>> /dev/nvme0n1p3 309248 368949247 368640000 175.8G Linux filesystem
>
>> total_bytes 188743680000
>
> OK, actually I'm wrong. 188743680000/512=368640000 sectors, which
> matches the GPT partition. So I'm not sure what happened.
>
The original error message (bad tree block start, want 1048576 have
6267530653245814412) means content of root node is wrong. 1048576 is
where btrfs "starts". If you cannot read that, you do not have any way
to reach other data. Likely something went wrong copying data.
>> ERROR: superblock bytenr 274877906944 is larger than device size 188743680000
>
> I don't see this value in the superblock.
>
This is the third superblock. "dump-super -a" may show it.
> What do you get for
>
> btrfs insp dump-s -f /dev/nvme0n1p3
> btfs insp dump-t -d /dev/nvme0n1p3
>
>
next prev parent reply other threads:[~2020-04-26 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 10:24 Help needed to recover from partition resize/move Yegor Yegorov
2020-04-25 20:05 ` Chris Murphy
2020-04-25 21:54 ` Yegor Yegorov
2020-04-26 0:56 ` Chris Murphy
2020-04-26 5:58 ` Andrei Borzenkov [this message]
2020-04-26 6:23 ` Yegor Yegorov
2020-04-26 7:36 ` Chris Murphy
2020-04-26 10:03 ` Andrei Borzenkov
2020-04-26 11:04 ` Ferry Toth
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=88488595-8392-c6e2-2784-84607c233d84@gmail.com \
--to=arvidjaar@gmail.com \
--cc=gochkin@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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