Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: K Chapman <mailbox@kchapman.de>, linux-btrfs@vger.kernel.org
Subject: Re: All Three Superblocks Damaged After Kernel Panic
Date: Tue, 12 Oct 2021 20:59:40 +0800	[thread overview]
Message-ID: <3a913681-58ee-6fe0-c414-3e33deafdf1e@gmx.com> (raw)
In-Reply-To: <8553dafa-14c5-b09f-d10f-83d995d062e0@kchapman.de>

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]



On 2021/10/12 18:35, K Chapman wrote:
> Qu,
>
> RE: If you don't have the tool to do it by your own, please send the 4K
> super block (dd if=/dev/mapper/home bs=1 skip=65536 count=4096
> of=/tmp/sb.dump) to me so I could do that for you.
>
> See attached.

Re-csumed super block is attached.

It passes my local test using btrfs-ins-dump-super.
Thus the csum should be correct.

Wish you good luck salvaging your data.

I would try mount with "-o ro,rescue=all" first, if no luck then
btrfs-restore --dry-run to see what can be salvaged.

But I doubt how many can be salvaged, consider how corrupted the backup
super blocks are.

Thanks,
Qu

>
> RE: Power loss and data writes.
>
> I believe the possibility is present but remote. I have not had a panic
> on x86 in many years during general work, this is more of an indication
> of some sort of problem than simply removing power at a bad time. It
> seems more likely, that for whatever reason, the kernel wrote spurious
> data to certain sectors, it will be interesting to see.
>
> Thank you!
>
> Kyle C.

[-- Attachment #2: sb.dump --]
[-- Type: application/octet-stream, Size: 4096 bytes --]

      reply	other threads:[~2021-10-12 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 14:13 All Three Superblocks Damaged After Kernel Panic Kyle James Chapman
2021-10-11 18:23 ` Matt Corallo
2021-10-11 23:22 ` Qu Wenruo
2021-10-12  7:41   ` K Chapman
2021-10-12 10:29     ` Qu Wenruo
2021-10-12 10:35       ` K Chapman
2021-10-12 12:59         ` Qu Wenruo [this message]

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=3a913681-58ee-6fe0-c414-3e33deafdf1e@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mailbox@kchapman.de \
    /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