From: Christoph Hellwig <hch@infradead.org>
To: Rafa?? Kupka <kupson@kupson.net>
Cc: 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: Fri, 2 Mar 2012 05:43:48 -0500 [thread overview]
Message-ID: <20120302104348.GA22230@infradead.org> (raw)
In-Reply-To: <1330539626.7615.73.camel@utemp.mieszkanie>
>From the trace this looks like we got incorrect results from xfs_imap,
which got some fairly significant changes between the two kernels
you tested. Can you check if 2.6.36 shows this issue? It's the first
kernel that had these big changes in inode lookup.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-02 10:43 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 [this message]
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
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=20120302104348.GA22230@infradead.org \
--to=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