From: Chris Mason <chris.mason@fusionio.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Chris Mason <clmason@fusionio.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BUG in btrfs_set_item_key_safe
Date: Fri, 26 Oct 2012 08:37:11 -0400 [thread overview]
Message-ID: <20121026123711.GC23729@shiny> (raw)
In-Reply-To: <508A824E.805@jan-o-sch.net>
On Fri, Oct 26, 2012 at 06:30:06AM -0600, Jan Schmidt wrote:
> On Fri, October 26, 2012 at 14:19 (+0200), Chris Mason wrote:
> > On Fri, Oct 26, 2012 at 12:35:43AM -0600, Jan Schmidt wrote:
> >> Hi,
> >>
> >> while running extensive qgroup and tree mod log tests I got to the following
> >> BUG, which is probably not related to tree mod log:
> >
> > So our keys are out of order...are you able to reproduce this?
>
> No reproducer yet. My tests ran fine for about 15 hours before that happened.
> I'll have an extensive amount of (tree mod log related) debug information if I
> should get there again.
>
> My guess is that it's not related to tree mod log, though, as there are tree log
> functions (fs/btrfs/tree-log.c) on the stack. I don't think rewinded buffers can
> make it there.
>
> I'll call back when I'll hit this again.
This is more likely to be memory corruption. I'd suggest turning on
slab debug and CONFIG_DEBUG_PAGE_ALLOC...hopefully you'll get a faster
crash.
-chris
next prev parent reply other threads:[~2012-10-26 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 6:35 BUG in btrfs_set_item_key_safe Jan Schmidt
2012-10-26 12:19 ` Chris Mason
2012-10-26 12:30 ` Jan Schmidt
2012-10-26 12:37 ` Chris Mason [this message]
2013-01-24 16:42 ` David Sterba
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=20121026123711.GC23729@shiny \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.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 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).