linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christian Wimmer <telefonchris@icloud.com>
Cc: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: is this the right place for a question on how to repair a broken btrfs file system?
Date: Fri, 6 Dec 2019 10:12:13 +0800	[thread overview]
Message-ID: <80206bf5-1475-0020-bad1-ebc96c57be84@gmx.com> (raw)
In-Reply-To: <BD72A51F-A536-428C-9993-91A43C99EE30@icloud.com>


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



On 2019/12/6 上午9:31, Christian Wimmer wrote:
> Hi Hugo and Qu,
> 
> here the output from the commands:
> 
> # btrfs ins dump-tree -t root /dev/sde1 2>&1
> btrfs-progs v4.19.1

Too old. Please use latest version btrfs-progs.

Just as mentioned, SLE is not a good choice for btrfs-progs.

Thanks,
Qu

> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> bad tree block 5349895454720, bytenr mismatch, want=5349895454720,
> have=14275350892879035392
> Couldn't setup device tree
> ERROR: unable to open /dev/sde1
> # 
> 
> 
> 
> # btrfs ins dump-tree -t extent /dev/sde1 2>&1 >/dev/null
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> bad tree block 5349895454720, bytenr mismatch, want=5349895454720,
> have=14275350892879035392
> Couldn't setup device tree
> ERROR: unable to open /dev/sde1
> # 
> 
> 
> # btrfs ins dump-tree -t chunk /dev/sde1
> btrfs-progs v4.19.1 
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> bad tree block 5349895454720, bytenr mismatch, want=5349895454720,
> have=14275350892879035392
> Couldn't setup device tree
> ERROR: unable to open /dev/sde1
> # 
> 
> 
> # btrfs ins dump-tree -t 5 /dev/sde1 2>&1 >/dev/null
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> checksum verify failed on 5349895454720 found B80B9FA8 wanted C61C3C00
> bad tree block 5349895454720, bytenr mismatch, want=5349895454720,
> have=14275350892879035392
> Couldn't setup device tree
> ERROR: unable to open /dev/sde1
> # 
> 
> 
> I will try to setup a newer kernel. Which Distro you would suggest for
> this purpose?
> The idea is to download and install a small linux just for recovery
> purpose for now.
> 
> Thanks,
> 
> Chris
> 
> 
> 
>> On 5. Dec 2019, at 21:04, Qu Wenruo <quwenruo.btrfs@gmx.com
>> <mailto:quwenruo.btrfs@gmx.com>> wrote:
>>
>> btrfs ins dump-tree -t root /dev/sde1 2>&1
> 


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

  parent reply	other threads:[~2019-12-06  2:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 20:00 is this the right place for a question on how to repair a broken btrfs file system? Christian Wimmer
2019-12-05 20:24 ` Hugo Mills
2019-12-05 20:42   ` Christian Wimmer
2019-12-06  0:04     ` Qu Wenruo
2019-12-06  1:32       ` Christian Wimmer
     [not found]       ` <BD72A51F-A536-428C-9993-91A43C99EE30@icloud.com>
2019-12-06  2:12         ` Qu Wenruo [this message]
2019-12-06  2:13         ` Qu Wenruo
     [not found]       ` <DBA30D34-E186-4359-A8C5-C13C870F1D81@icloud.com>
2019-12-06  3:49         ` Qu Wenruo
2019-12-06 21:28           ` Christian Wimmer
2019-12-05 22:01   ` Christian Wimmer

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=80206bf5-1475-0020-bad1-ebc96c57be84@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=telefonchris@icloud.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).