All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Chris Mason <chris.mason@oracle.com>,
	Josef Bacik <josef@redhat.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs failing fsx-linux
Date: Thu, 3 Sep 2009 09:10:11 +0200	[thread overview]
Message-ID: <20090903071011.GA979@wotan.suse.de> (raw)
In-Reply-To: <20090902190721.GA4043@think>

On Wed, Sep 02, 2009 at 03:07:21PM -0400, Chris Mason wrote:
> On Wed, Sep 02, 2009 at 07:14:50PM +0200, Nick Piggin wrote:
> > On Tue, Aug 18, 2009 at 01:59:50PM -0400, Josef Bacik wrote:
> > > I'll take a look at this later today and see what I can come up with.  Thanks
> > > for reporting it.
> > 
> > Any progress with this? Were you able to reproduce?
> > 
> 
> I thought this was where the rb tree patch came from, sorry.  I'll try
> to reproduce.

Oh, I must not have been clear: I first hit the rbtree bug, then when
that was fixed, the same workload was eventually showing up fsx-linux
failures (but no more kernel crashes).


  reply	other threads:[~2009-09-03  7:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18 17:26 btrfs failing fsx-linux Nick Piggin
2009-08-18 17:59 ` Josef Bacik
2009-08-19  8:50   ` Nick Piggin
2009-09-02 17:14   ` Nick Piggin
2009-09-02 17:29     ` Josef Bacik
2009-09-02 19:07     ` Chris Mason
2009-09-03  7:10       ` Nick Piggin [this message]
2009-09-09 13:13 ` Chris Mason
2009-09-09 13:34   ` Nick Piggin
2009-09-09 13:37     ` Chris Mason
2009-09-09 13:43       ` Nick Piggin
2009-09-09 13:47         ` Chris Mason
2009-09-11 19:36 ` Chris Mason

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=20090903071011.GA979@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=chris.mason@oracle.com \
    --cc=josef@redhat.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 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.