linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel traces
Date: Wed, 12 Dec 2018 14:01:52 -0700	[thread overview]
Message-ID: <CAJCQCtSCcM0YTtp0f1i=FmrFigsfJEsr+Excwm=YHx4_wN49gg@mail.gmail.com> (raw)
In-Reply-To: <20181212072614.GA9188@cuci.nl>

On Wed, Dec 12, 2018 at 12:26 AM Stephen R. van den Berg <srb@cuci.nl> wrote:
>
> Chris Murphy wrote:
> >Also, what scheduler are you using? And do you get different results
> >with a different one (better or worse)?
>
> I'm using CFQ, and I don't think I ever tried a different one.
> But, btrfs should be compatible with all schedulers.

Sure but there are some workloads we know where CFQ can cause or
exacerbate problems with some storage stacks, and other schedulers
exist to deal with those workloads better. So the question is whether
the problem is made worse or better by trying another scheduler. It
might have no effect. And it might just flat out be a Btrfs bug, but
I'm doing send and receive on far more meager hardware with much less
RAM and haven't run into problems.

But yeah, one of the developers might have more to say about it once
sysrq+w output is available, which should expose what's stuck or busy.


-- 
Chris Murphy

  reply	other threads:[~2018-12-12 21:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 12:05 Kernel traces Stephen R. van den Berg
2018-12-10 16:54 ` Chris Murphy
2018-12-11 11:52   ` Stephen R. van den Berg
2018-12-12  6:16     ` Chris Murphy
2018-12-12  7:26       ` Stephen R. van den Berg
2018-12-12 21:01         ` Chris Murphy [this message]
2018-12-28  9:20           ` Stephen R. van den Berg
2018-12-28 10:10             ` Qu Wenruo
2018-12-28 13:40               ` Stephen R. van den Berg
2018-12-28 13:46                 ` Qu Wenruo
2018-12-28 15:00                   ` Stephen R. van den Berg
2019-01-23 15:50                     ` Stephen R. van den Berg
2019-01-25  8:01                       ` New hang (Re: Kernel traces), sysreq+w output Stephen R. van den Berg
2019-01-25  8:04                         ` Stephen R. van den Berg
2019-02-05 22:18                         ` Stephen R. van den Berg
2019-02-06  0:22                           ` Qu Wenruo
2019-02-06  0:36                             ` Martin Raiber
2019-07-26 16:31               ` qgroup: Don't trigger backref walk at delayed ref insert time (Re: Kernel traces) Stephen R. van den Berg
2019-07-26 23:24                 ` Qu Wenruo
2018-12-11 15:21 Kernel traces Tomasz Chmielewski

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='CAJCQCtSCcM0YTtp0f1i=FmrFigsfJEsr+Excwm=YHx4_wN49gg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=srb@cuci.nl \
    /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).