All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Jim Schutt <jaschut@sandia.gov>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent_io.c:3982!
Date: Tue, 10 Apr 2012 16:24:40 -0400	[thread overview]
Message-ID: <20120410202440.GZ29506@shiny> (raw)
In-Reply-To: <4F848C62.6030100@sandia.gov>

On Tue, Apr 10, 2012 at 01:39:14PM -0600, Jim Schutt wrote:
> Hi,
> 
> I hit this BUG today.
> 
> I'm running 3.3.1 merged with the ceph and btrfs bits for 3.4,
> i.e. 3.3.1 +
>   commit bc3f116fec194 "Btrfs: update the checks for mixed block groups with big metadata blocks"
>   commit c666601a935b9 "rbd: move snap_rwsem to the device, rename to header_rwsem"
> 
> The btrfs filesystem in question is backing a Ceph OSD under
> a heavy write load.
> 
> Here's the bug:
> 
> [510342.517157] ------------[ cut here ]------------
> [510342.521855] kernel BUG at fs/btrfs/extent_io.c:3982!

Could you please confirm that line number is this BUG_ON()

        BUG_ON(extent_buffer_under_io(eb));

Josef has a theory on this one, but I want to make sure we're chasing
the right thing.

-chris

  reply	other threads:[~2012-04-10 20:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 19:39 kernel BUG at fs/btrfs/extent_io.c:3982! Jim Schutt
2012-04-10 20:24 ` Chris Mason [this message]
2012-04-10 20:32   ` Jim Schutt
2012-04-11 19:09 ` Josef Bacik
2012-04-11 20:24   ` Jim Schutt
2012-04-11 20:28     ` Josef Bacik
2012-04-11 21:39       ` Jim Schutt
2012-04-12  0:29         ` Chris Mason
2012-05-01 16:00     ` Josef Bacik
2012-05-01 16:41       ` Jim Schutt
2012-05-03 14:43         ` Jim Schutt
2012-05-03 14:53           ` Josef Bacik
2012-05-03 15:46             ` [EXTERNAL] " Jim Schutt
2012-05-03 15:53               ` Josef Bacik

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=20120410202440.GZ29506@shiny \
    --to=chris.mason@oracle.com \
    --cc=jaschut@sandia.gov \
    --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 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.