2009/1/10 Alexander Beregalov <a.beregalov@xxxxxxxxx>: > 2009/1/10 Alexander Beregalov <a.beregalov@xxxxxxxxx>: >> 2009/1/10 Alexander Beregalov <a.beregalov@xxxxxxxxx>: >>> 2009/1/9 Dave Chinner <david@xxxxxxxxxxxxx>: >>>> On Fri, Jan 09, 2009 at 07:41:21AM +0300, Alexander Beregalov wrote: >>>> Looks like the same btree corruption problem as this: >>>> >>>> http://oss.sgi.com/archives/xfs/2009-01/msg00118.html >>>> >>>> We're working to find the cause right now, but I find it interesting >>>> that you are running a CONFIG_XFS_DEBUG=y kernel and the first >>>> point that something is found wrong is the same place that the >>>> above non-debug case is detecting corruption. >>>> >>>> Can you reproduce it/have a reproducable test case? >>> Yes, it is easy reproducible for me, it happens every time I run >>> `rtorrent` during few minutes after boot. >>> I will try to provide simpler testcase. It is hard to bisect it, These are last good and bad commits: good: [854929f05831d3a290a802815ee955b96c740c61] [XFS] add new btree statistics bad: [7f7c39ccb6045cf1fd5e7684a484c445291b44d4] [XFS] make btree tracing generic -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
