All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Josef Bacik <JBacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"daniel@quora.org" <daniel@quora.org>,
	"Chris L. Mason" <clmason@fusionio.com>,
	"sensille@gmx.net" <sensille@gmx.net>
Subject: Re: [PATCH] Btrfs: allow delayed refs to be merged
Date: Thu, 12 Jul 2012 13:05:21 -0400	[thread overview]
Message-ID: <20120712170521.GE2059@localhost.localdomain> (raw)
In-Reply-To: <4FFD7D61.8070502@jan-o-sch.net>

On Wed, Jul 11, 2012 at 07:19:29AM -0600, Jan Schmidt wrote:
> Hi Josef,
> 
> I hit a warning with this patch on top of the current cmason/for-linus
> branch. Takes about 15 minutes to produce when running xfstest 278 in
> a loop and, in another shell, doing fsstress on the same volume to
> force metadata modifications.
> 
> fs/btrfs/extent-tree.c
> ...
> 5032         } else if (ret == -ENOENT) {
> 5033                 btrfs_print_leaf(extent_root, path->nodes[0]);
> 5034                 WARN_ON(1);
> 5035                 printk(KERN_ERR "btrfs unable to find ref byte nr %llu "
> 5036                        "parent %llu root %llu  owner %llu offset %llu\n",
> 5037                        (unsigned long long)bytenr,
> 5038                        (unsigned long long)parent,
> 5039                        (unsigned long long)root_objectid,
> 5040                        (unsigned long long)owner_objectid,
> 5041                        (unsigned long long)owner_offset);
> 5042         } else {
> 

Which test, 278 is an xfs specific test.  Thanks,

Josef

  reply	other threads:[~2012-07-12 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 18:52 [PATCH] Btrfs: allow delayed refs to be merged Josef Bacik
2012-07-10 19:39 ` Arne Jansen
2012-07-10 19:52   ` Josef Bacik
2012-07-11 13:19 ` Jan Schmidt
2012-07-12 17:05   ` Josef Bacik [this message]
2012-07-12 18:41     ` Jan Schmidt

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=20120712170521.GE2059@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=daniel@quora.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list.btrfs@jan-o-sch.net \
    --cc=sensille@gmx.net \
    /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.