From: Andy Isaacson <adi@hexapodia.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Drunkard Zhang <gongfan193@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.37 BUG at inode.c:1616 (was Re: 2.6.37: Bug on btrfs while umount)
Date: Mon, 10 Jan 2011 11:34:37 -0800 [thread overview]
Message-ID: <20110110193437.GA19021@hexapodia.org> (raw)
In-Reply-To: <20110110080815.GA7508@hexapodia.org>
On Mon, Jan 10, 2011 at 12:08:15AM -0800, Andy Isaacson wrote:
> On Thu, Jan 06, 2011 at 08:29:12PM -0500, Chris Mason wrote:
> > > [50010.838804] ------------[ cut here ]------------
> > > [50010.838931] kernel BUG at fs/btrfs/inode.c:1616!
> > > [50010.839053] invalid opcode: 0000 [#1] PREEMPT SMP
> [snip]
> > > [50010.839653] Pid: 1681, comm: btrfs-endio-wri Not tainted 2.6.37 #1
> >
> > Could you please pull from the master branch of the btrfs unstable tree.
> > We had a late fix that is related to this.
>
> I saw BUG at inode.c:1616 while running 2.6.37-rc6-11882-g55ec86f, I saw
Just got this again, same BUG and same stack trace. This machine +
fs ran great for several months under approximately the same workload,
but the FS is slowly filling up; is this a regression in .37 or is the
bug a function of the FS load?
-andy
prev parent reply other threads:[~2011-01-10 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 1:25 2.6.37: Bug on btrfs while umount Drunkard Zhang
2011-01-07 1:29 ` Chris Mason
2011-01-07 1:36 ` Drunkard Zhang
2011-01-10 8:08 ` 2.6.37 BUG at inode.c:1616 (was Re: 2.6.37: Bug on btrfs while umount) Andy Isaacson
2011-01-10 19:34 ` Andy Isaacson [this message]
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=20110110193437.GA19021@hexapodia.org \
--to=adi@hexapodia.org \
--cc=chris.mason@oracle.com \
--cc=gongfan193@gmail.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).