From: Josef Bacik <jbacik@fusionio.com>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: Josef Bacik <jbacik@fusionio.com>,
Stefan Behrens <sbehrens@giantdisaster.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel BUG on Snapshot Deletion (3.11.0-rc5)
Date: Wed, 21 Aug 2013 09:59:05 -0400 [thread overview]
Message-ID: <20130821135905.GL3990@localhost.localdomain> (raw)
In-Reply-To: <CAKcLGm_jFa_2FaaaudRZF8JRymh1t3ASMFN1tFGbs0PGt1vNaQ@mail.gmail.com>
On Wed, Aug 21, 2013 at 08:44:55AM -0500, Mitch Harder wrote:
> On Thu, Aug 15, 2013 at 12:29 PM, Mitch Harder
> <mitch.harder@sabayonlinux.org> wrote:
> > I'm running into a curious problem.
> >
> > In the process of making my script portable, I am breaking the ability
> > to replicate the error.
> >
> > I'm trying to isolate the aspect of my local script that is triggering
> > the error. No firm insights yet.
> >
> >
> > On Tue, Aug 13, 2013 at 11:03 AM, Mitch Harder
> > <mitch.harder@sabayonlinux.org> wrote:
> >> Let me work on making that script more portable, and hopefully quicker
> >> to reproduce.
> >>
> >> On Tue, Aug 13, 2013 at 9:15 AM, Josef Bacik <jbacik@fusionio.com> wrote:
> >>> On Mon, Aug 12, 2013 at 11:06:27PM -0500, Mitch Harder wrote:
> >>>> I'm hitting a btrfs Kernel BUG running a snapshot stress script with
> >>>> linux-3.11.0-rc5.
> >>>>
> >>>
> >>> I can haz script? Thanks,
> >>>
>
> I've had a hard time assembling a portable reproducer for this issue.
>
> I discovered that my reproducer was highly dependent on a local
> archive of out-of-date git kernel sources. My efforts to reproduce
> the error with a portable set of scripts with publicly available
> kernel git sources weren't successful.
>
> It seems like this issue is related to a corner-case workload that is
> difficult to reproduce.
>
> So I've bisected the error I was seeing with my local script, and
> identified the following commit as triggering my issue:
>
> commit: 3c64a1aba7cfcb04f79e76f859b3d66660275d59
> Btrfs: cleanup: don't check the same thing twice
> https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/fs/btrfs?h=for-linus&id=3c64a1aba7cfcb04
>
> I tested a kernel which reverted this change, and also added WARN_ON
> lines to provide a back trace.
>
Well that works too :). I'll look at this when I get back from the doctor in a
few hours and see if I can't figure out why it started happening. Thanks,
Josef
next prev parent reply other threads:[~2013-08-21 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 4:06 Kernel BUG on Snapshot Deletion (3.11.0-rc5) Mitch Harder
2013-08-13 14:15 ` Josef Bacik
2013-08-13 16:03 ` Mitch Harder
2013-08-15 17:29 ` Mitch Harder
2013-08-21 13:44 ` Mitch Harder
2013-08-21 13:59 ` Josef Bacik [this message]
2013-08-21 14:04 ` Josef Bacik
2013-08-23 8:48 ` Stefan Behrens
2013-08-23 16:22 ` Mitch Harder
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=20130821135905.GL3990@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mitch.harder@sabayonlinux.org \
--cc=sbehrens@giantdisaster.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 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).