From: Dave Chinner <david@fromorbit.com>
To: "Rafał Kupka" <kupson@kupson.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: XFS: Assertion failed: bp->b_bn != XFS_BUF_DADDR_NULL, file: fs/xfs/xfs_buf.c, line: 598
Date: Wed, 7 Mar 2012 07:30:20 +1100 [thread overview]
Message-ID: <20120306203020.GG3592@dastard> (raw)
In-Reply-To: <1330983612.28645.18.camel@utemp.mieszkanie>
On Mon, Mar 05, 2012 at 10:40:12PM +0100, Rafał Kupka wrote:
> On Sat, 2012-03-03 at 06:44 -0500, Christoph Hellwig wrote:
> > On Sat, Mar 03, 2012 at 12:37:07PM +0100, Rafa?? Kupka wrote:
> > > On Fri, 2012-03-02 at 05:43 -0500, Christoph Hellwig wrote:
> Hi,
>
> I've completed bisection process. It looks like kernel up to
>
> 704b2907 "xfs: register the inode cache shrinker before quotachecks"
>
> is good and first bad commit is:
>
> 0e6e847f "xfs: stop using the page cache to back the buffer cache"
Which changed internals of the buffer cache, but not the external
interfaces.
> I double tested it - 704b2907 can do 60+ loops of xfsdump without any
> trouble and 0e6e847f breaks in <10 iterations.
What is your test case?
Also, it might be worthwhile to capture an event trace (e.g. all the
xfs_buf events) to see what occurs just before the error is
triggered. That might tell us exactl what sequence has occurred
leading up to the error.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-06 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 18:20 XFS: Assertion failed: bp->b_bn != XFS_BUF_DADDR_NULL, file: fs/xfs/xfs_buf.c, line: 598 Rafał Kupka
2012-03-02 10:43 ` Christoph Hellwig
2012-03-03 11:37 ` Rafał Kupka
2012-03-03 11:44 ` Christoph Hellwig
2012-03-05 21:40 ` Rafał Kupka
2012-03-06 20:30 ` Dave Chinner [this message]
2012-03-08 19:10 ` Rafał Kupka
2012-03-26 16:05 ` Rafał Kupka
2012-03-27 3:28 ` Dave Chinner
2012-03-27 10:17 ` Dave Chinner
2012-03-30 16:02 ` Rafał Kupka
2012-04-04 9:19 ` Rafał Kupka
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=20120306203020.GG3592@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=kupson@kupson.net \
--cc=xfs@oss.sgi.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