From: Josef Bacik <jbacik@fusionio.com>
To: Rock Lee <zimilo@code-trick.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: HIT WARN_ON WARNING: at fs/btrfs/extent-tree.c:6339 btrfs_alloc_free_block+0x126/0x330 [btrfs]()
Date: Wed, 19 Dec 2012 10:29:25 -0500 [thread overview]
Message-ID: <20121219152925.GC4033@localhost.localdomain> (raw)
In-Reply-To: <CAMRmmp+=YT_-KdGHRWo5GrofiSnkZB_xVpN1Z8Jp4xgo0fVS3A@mail.gmail.com>
On Wed, Dec 19, 2012 at 08:12:01AM -0700, Rock Lee wrote:
> Hi all,
>
> Did someone have met this problem before. When doing the tests, I hit
>
> the WARN_ON. Is this log make sense or someone had fixed the problem.
>
> If needed, I can supply the detail log and the testcase source file.
>
> Version: the latest codes at linus git tree.
>
If you can give me your testcase I will love you forever. Thanks,
Josef
next prev parent reply other threads:[~2012-12-19 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 15:12 HIT WARN_ON WARNING: at fs/btrfs/extent-tree.c:6339 btrfs_alloc_free_block+0x126/0x330 [btrfs]() Rock Lee
2012-12-19 15:27 ` cwillu
2012-12-19 15:29 ` Josef Bacik [this message]
2012-12-19 15:59 ` Rock Lee
2012-12-20 14:46 ` Rock Lee
2012-12-20 14:49 ` Rock Lee
2012-12-20 16:34 ` 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=20121219152925.GC4033@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zimilo@code-trick.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