All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs failing fsx-linux
Date: Fri, 11 Sep 2009 15:36:18 -0400	[thread overview]
Message-ID: <20090911193618.GD2894@think> (raw)
In-Reply-To: <20090818172641.GC30325@wotan.suse.de>

On Tue, Aug 18, 2009 at 07:26:41PM +0200, Nick Piggin wrote:
> Hi Chris,
> 
> Don't know if this is a known issue, but I have btrfs (after my previous
> inode_tree fixup patch) failing fsx-linux in Linus's current git tree.

Thanks for your help on this Nick, I've got my current fixes for fsx in
the master branch of the btrfs-unstable repo:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git

If you're curious, the 3 most relevant commits are here:

http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=commit;h=93c82d575055f1bd0277acae6f966bebafd80dd5

http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=commit;h=50a9b214bc6c052caa05a210ebfc1bdf0d7085b2

http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-unstable.git;a=commit;h=a1ed835e1ab5795f91b198d08c43e2f56848dcf3

But these fixes are built on top of my performance work (which was sure
to break fsx on its own).

-chris

      parent reply	other threads:[~2009-09-11 19:36 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
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 [this message]

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=20090911193618.GD2894@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=npiggin@suse.de \
    /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.