From: Chris Murphy <lists@colorremedies.com>
To: Zirconium Hacker <jared.e.vb@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: btrfs balance hangs
Date: Fri, 5 Apr 2019 00:39:09 -0600 [thread overview]
Message-ID: <CAJCQCtRv2gnTtAm02jsbeiKpX-s8W8BO9SdA5topJ92op_C_hw@mail.gmail.com> (raw)
In-Reply-To: <CALsQ4_zTUdFCTunnu5NVpAu1-kP0y319szRHdqbnKG8--2-xEQ@mail.gmail.com>
On Thu, Apr 4, 2019 at 11:24 PM Zirconium Hacker <jared.e.vb@gmail.com> 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.
What do you get for:
# btrfs insp dump-s -f /dev/
# btrfs insp dump-t -b 2629033574400 /dev/
The csum test doesn't complain so that suggests any corruption happens
before csum is calculated and written. It could be a bug, however we
also have a wanted transid that is lower than what's found (finds a
transid in the future). That's a bug no matter what, either the drive
firmware has some bug or Btrfs, and I would expect the firmware can't
be responsible for such a huge transid difference. But yeah maybe Qu
has an idea, also he knows about qgroups, I don't know anything about
them other than it can make things very slow. There are some fixes on
the way soon but it doesn't really help today.
--
Chris Murphy
next prev parent reply other threads:[~2019-04-05 6:39 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 [this message]
2019-04-05 7:15 ` Qu Wenruo
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=CAJCQCtRv2gnTtAm02jsbeiKpX-s8W8BO9SdA5topJ92op_C_hw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=jared.e.vb@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).