From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Zirconium Hacker <jared.e.vb@gmail.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs balance hangs
Date: Fri, 5 Apr 2019 15:15:57 +0800 [thread overview]
Message-ID: <59080b24-a005-8066-c7c5-b2108e23dbbb@gmx.com> (raw)
In-Reply-To: <CALsQ4_zTUdFCTunnu5NVpAu1-kP0y319szRHdqbnKG8--2-xEQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
On 2019/4/5 下午1:24, Zirconium Hacker wrote:
> I've actually had a check running for the past 10 hours or so.
> It got far enough, so I stopped it. The output is attached.
>
Unfortunately, your fs indeed get corrupted, but only in extent tree.
You should be able to mount the fs in RO mode and copy out the data.
But I'm surprised that balance by somehow corrupted the metadata CoW.
Would you mind to paste the output of the following command?
# btrfs ins dump-super /dev/sdh1
# btrfs ins dump-tree -b 2629033574400 /dev/sdh1
If the output of the 2nd command contains filenames, feel free to remove
filenames.
I'm just interested in which tree btrfs is trying to write into existing
tree blocks, maybe it has some clue (e.g log tree/reloc tree).
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-05 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 16:11 btrfs balance hangs Zirconium Hacker
2019-04-01 16:43 ` Chris Murphy
2019-04-04 18:17 ` Zirconium Hacker
2019-04-05 3:04 ` Chris Murphy
2019-04-05 5:24 ` Zirconium Hacker
2019-04-05 6:39 ` Chris Murphy
2019-04-05 7:15 ` Qu Wenruo [this message]
2019-04-09 0:12 ` Zirconium Hacker
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=59080b24-a005-8066-c7c5-b2108e23dbbb@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=jared.e.vb@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;
as well as URLs for NNTP newsgroup(s).