linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: 2.6.29-rc2 oops and assertion failure...
Date: Thu, 07 Apr 2011 12:23:14 -0400	[thread overview]
Message-ID: <4D9DE4F2.1050909@redhat.com> (raw)
In-Reply-To: <BANLkTikJJFqEs0F_wPdTinct0k_4uLh1hQ@mail.gmail.com>

On 04/07/2011 03:21 AM, Daniel J Blueman wrote:
> When running a practical stress-test on 2.6.29-rc2 trying to reproduce
> an older (extent refcounting) issue, I am consistently able to hit an
> oops [1] and an assertion failure [2].
>

Sorry about that, please apply the patch I just sent this morning

[PATCH] Btrfs: deal with the case that we run out of space in the cache

Thanks,

Josef

  reply	other threads:[~2011-04-07 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07  7:21 2.6.29-rc2 oops and assertion failure Daniel J Blueman
2011-04-07 16:23 ` Josef Bacik [this message]
2011-04-08  2:26   ` Daniel J Blueman
2011-04-08 13:37     ` 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=4D9DE4F2.1050909@redhat.com \
    --to=josef@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=daniel.blueman@gmail.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;
as well as URLs for NNTP newsgroup(s).