On Sat, Jan 10, 2009 at 03:19:00PM +0300, Alexander Beregalov wrote: > 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 That would be odd as 7f7c39ccb6045cf1fd5e7684a484c445291b44d4 only changes the tracing code which currently isn't enabled. Or we get some sort of miscompilation due slightly different noop macros. How big is the filesystem where you see this corruption? Maybe I could reproduce it locally with a xfs_metadump image. > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs ---end quoted text--- -- 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
