Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: warn at fs/btrfs/extent-tree.c:5748 __btrfs_free_extent+0x9ce/0xa20
Date: Wed, 12 Mar 2014 07:54:30 +0000 (UTC)	[thread overview]
Message-ID: <pan$160f2$a0461d09$c8460df4$fac5305e@cox.net> (raw)
In-Reply-To: alpine.DEB.2.00.1403111642350.5511@cobra.newdream.net

Sage Weil posted on Tue, 11 Mar 2014 16:44:40 -0700 as excerpted:

> Is this something you guys have seen before?  This is from v3.13-rc2.
> 
> [49432.777445] CPU: 3 PID: 26411 Comm: ceph-osd
> Tainted: GF         I  3.14.0-rc5-ceph-00016-gf31a96a #

v3.13-rc2?

1) That's a bit old as there's actually several 3.13 stable releases now.

2) It doesn't appear correct anyway, since the trace reports 3.14-rc5+

(Meanwhile, I'm not a dev so no comment on the root question.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-03-12  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 23:44 warn at fs/btrfs/extent-tree.c:5748 __btrfs_free_extent+0x9ce/0xa20 Sage Weil
2014-03-12  7:54 ` Duncan [this message]
2014-03-14 15:27 ` Josef Bacik
2014-03-14 15:34   ` Sage Weil
2014-03-14 15:35     ` Josef Bacik
2014-03-14 15:52       ` Filipe David Manana

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$160f2$a0461d09$c8460df4$fac5305e@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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