From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Michael Post <michael_post@web.de>,
Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs@vger.kernel.org
Subject: Re: Urgent: Need BTRFS-Expert
Date: Thu, 18 Oct 2018 08:48:03 +0800 [thread overview]
Message-ID: <c35d0b80-ba1f-5c4b-c886-c3b17c717c5b@gmx.com> (raw)
In-Reply-To: <1cc35c0e-3ea2-e63f-b42e-084f44b77ffd@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]
On 2018/10/17 下午11:50, Michael Post wrote:
> Hello Qu,
> Hello Hugo,
>
> i got this result when i try to recover the chunk tree.
>
> # btrfs check /dev/mapper/vg0-virtualbox
> bytenr mismatch, want=1263835381760, have=0
> ERROR: cannot open file system
This means some essential trees get corrupted.
I remember latest btrfs-progs should prompt which tree is corrupted.
Would you please use latest btrfs-progs and try again?
Also would you please paste the following output?
# btrfs ins dump-super <device>
# btrfs ins dump-tree -t chunk <device>
Thanks,
Qu
>
>
> # btrfs rescue chunk-recover -y /dev/mapper/vg0-virtualbox
> Scanning: DONE in dev0
> open with broken chunk error
> Chunk tree recovery failed
>
> Did you any clue?
>
>
> Michael
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-10-18 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 7:58 Urgent: Need BTRFS-Expert Michael Post
2018-10-17 8:17 ` Michael Post
2018-10-17 9:18 ` Hugo Mills
2018-10-17 9:27 ` Michael Post
2018-10-17 10:39 ` Qu Wenruo
2018-10-17 15:50 ` Michael Post
2018-10-18 0:48 ` 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=c35d0b80-ba1f-5c4b-c886-c3b17c717c5b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=michael_post@web.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;
as well as URLs for NNTP newsgroup(s).