From: Christoph Hellwig <hch@infradead.org>
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: Sat, 3 Mar 2012 06:44:13 -0500 [thread overview]
Message-ID: <20120303114413.GA18748@infradead.org> (raw)
In-Reply-To: <1330774627.32457.24.camel@utemp.mieszkanie>
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:
> Hello,
>
> > 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.
>
> I've tested more kernels and here are results (linus git tree, no
> additional patches):
> - v2.6.36 -- good
> - v2.6.38 -- good
> - v2.6.39 -- bad, I/O error log entry and locked processes:
> - git revision 243b422af9ea9af4ead07a8ad54c90d4f9b6081a -- good
> It's one patch before "xfs: preallocation transactions do not need to be synchronous"
>
> - git revision c5850150d0b9ae16840c5d9846f9d5a759996a15:
> Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs
>
> * 'for-linus' of git://oss.sgi.com/xfs/xfs:
> xfs: stop using the page cache to back the buffer cache
> xfs: register the inode cache shrinker before quotachecks
> xfs: xfs_trans_read_buf() should return an error on failure
This is the only patch in that area. Give me a bit more time to
figure out how it could related to your issues.
> Hung xfsdump (only?) without any additional log entries
> (CONFIG_XFS_DEBUG is set):
> I don't know if it's the same bug - there is no assertion nor I/O error
> log entry...
It's the same code path at least..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-03 11:44 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 [this message]
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=20120303114413.GA18748@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