linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Ravi Pinjala <pstatic@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs crash
Date: Tue, 16 Nov 2010 09:46:38 -0500	[thread overview]
Message-ID: <1289918733-sup-3634@think> (raw)
In-Reply-To: <AANLkTikAPcS3aeUp14hDJY8RTh_HnSg6sSR1Eyj+RNzM@mail.gmail.com>

Excerpts from Ravi Pinjala's message of 2010-11-14 12:31:35 -0500:
> I got the following crash on one of my Ceph nodes this morning. I
> don't know how to reproduce it yet; I was just wondering if it was a
> known issue. This is with the latest kernel for Ubuntu 10.10.
> 
> Nov 13 19:21:21 alpha kernel: [19432.396679] ------------[ cut here
> ]------------
> Nov 13 19:21:22 alpha kernel: [19432.396732] WARNING: at
> /build/buildd/linux-2.6.35/fs/btrfs/extent-tree.c:5322

This warning should have been followed by a printk:

        WARN_ON(1);
        printk(KERN_INFO"block_rsv size %llu reserved %llu freed %llu %llu\n",
                block_rsv->size, block_rsv->reserved,
                block_rsv->freed[0], block_rsv->freed[1]);

        return ERR_PTR(-ENOSPC);

Do you have the printk?

Josef did some work here, so we have a number of related fixes in the
current git tree.

-chris

  reply	other threads:[~2010-11-16 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 17:31 btrfs crash Ravi Pinjala
2010-11-16 14:46 ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-16 10:40 BTRFS crash Cornea, Alexandru
2012-04-19 17:28 btrfs crash Jonas H.
2008-08-23 13:37 Priit Laes
2008-08-23 19:20 ` 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=1289918733-sup-3634@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=pstatic@gmail.com \
    /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).