Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs scrub under linux with ck-patchset - oops
Date: Fri, 8 May 2015 10:25:00 +0000 (UTC)	[thread overview]
Message-ID: <pan.2015.05.08.10.25.00@googlemail.com> (raw)
In-Reply-To: 20150508101002.GA3945@sune

On Fri, 08 May 2015 11:10:02 +0100, Leonidas Spyropoulos wrote:

> Does anyone experience issues with I/O intensive operations using btrfs
> and BFQ io scheduler? I had a kernel panic while running (almost at the
> start) a scrub and I glimpsed the elevator.c filename on the kernel dump
> before I had to hard-reset.

You may want to check the BFQ list, specifically [1]. It seems to be a
bug in BFQ itself and unrelated to btrfs.

-h

[1] https://groups.google.com/forum/#!topic/bfq-iosched/3T0t2JWl3bk



      reply	other threads:[~2015-05-08 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 10:10 btrfs scrub under linux with ck-patchset - oops Leonidas Spyropoulos
2015-05-08 10:25 ` Holger Hoffstätte [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=pan.2015.05.08.10.25.00@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=linux-btrfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox