From: Dave Jones <davej@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-btrfs@vger.kernel.org
Subject: Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()
Date: Mon, 17 Jun 2013 14:58:10 -0400 [thread overview]
Message-ID: <20130617185810.GA13370@redhat.com> (raw)
In-Reply-To: <20130617184227.15057.75499@localhost.localdomain>
On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote:
> Quoting Dave Jones (2013-06-17 14:20:06)
> > On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote:
> > > Quoting Dave Jones (2013-06-17 09:49:55)
> > > > Hit this while running this script in a loop..
> > > > https://github.com/kernelslacker/io-tests/blob/master/setup.sh
> > > > [34385.251507] ------------[ cut here ]------------
> > > > [34385.254068] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()
> > >
> > > Thanks Dave, how long did you have to run the script to trigger it?
> > >
> > > -chris
> >
> > Judging by the timestamp, about 9 hours. This is on a 3 disk (sata)
> > (oldish) quad opteron. Might repro faster on a more modern machine.
>
> Exactly how did you run it? I want to make sure I'm matching your
> config.
while [ 1 ];
do
setup.sh
done
You'll need to set DISK1 etc variables at the top of the script to point to
at least 3 disks for it to scribble over.
you'll also need fsx and fsstress in /usr/local/bin.
Think that's all.
Dave
next prev parent reply other threads:[~2013-06-17 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 13:49 [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]() Dave Jones
2013-06-17 17:39 ` Chris Mason
2013-06-17 18:20 ` Dave Jones
2013-06-17 18:42 ` Chris Mason
2013-06-17 18:58 ` Dave Jones [this message]
2013-06-19 18:02 ` Chris Mason
2013-06-19 18:34 ` Dave Jones
2013-06-19 18:42 ` Chris Mason
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=20130617185810.GA13370@redhat.com \
--to=davej@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).