All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: 5.4.8: WARNING: errors detected during scrubbing, corrected
Date: Fri, 10 Jan 2020 10:03:57 -0500	[thread overview]
Message-ID: <5b11d0a5-b1be-decb-bc74-5b28866637ee@toxicpanda.com> (raw)
In-Reply-To: <20200109162839.GA29989@merlins.org>

On 1/9/20 11:28 AM, Marc MERLIN wrote:
> Howdy,
> 
> I have 6 btrfs pools on my laptop on 3 different SSDs.
> After a few years, one of them is now very slow to scrub
> and hands my laptop while it runs.
> This started under 5.3.8, but upgrading to 5.4.8 didn't fix it.
> 

What the hell kind of laptop are you running that has 3 different SSDs?  That 
thing has got to weight a ton.

> Also, it output 'errors during scrubbing', but I see nothing in the kernel log:
> btrfs scrub start -Bd /mnt/btrfs_pool2
> scrub device /dev/mapper/pool2 (id 1) done
>          scrub started at Thu Jan  9 01:46:45 2020 and finished after 01:29:49
>          total bytes scrubbed: 1.27TiB with 0 errors
> WARNING: errors detected during scrubbing, corrected
> 
> real    89m49.190s
> user    0m0.000s
> sys     13m26.548s
> 
> 
> 89mn is also longer than normal

Can you run the bcc tool offcputime

https://github.com/iovisor/bcc/blob/master/tools/offcputime.py

while scrub is running to get a few stack traces of where we're spending all of 
our time?  It'll help narrow down who is to blame.  Thanks,

Josef

  reply	other threads:[~2020-01-10 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 16:28 5.4.8: WARNING: errors detected during scrubbing, corrected Marc MERLIN
2020-01-10 15:03 ` Josef Bacik [this message]
2020-01-10 16:22   ` Marc MERLIN

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=5b11d0a5-b1be-decb-bc74-5b28866637ee@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.