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. >> > > This time I get it during log replaing before mounting. > > * Mounting local filesystems... > [ 214.039447] XFS mounting filesystem sda3 > [ 214.190773] Ending clean XFS mount for filesystem: sda3 > [ 214.321525] XFS mounting filesystem sdb1 > [ 214.453029] Starting XFS recovery on filesystem: sdb1 (logdev: internal) > [ 215.062964] Ending XFS recovery on filesystem: sdb1 (logdev: internal) > [ 215.163358] Assertion failed: fs_is_ok, file: fs/xfs/xfs_btree.c, line: 3327 Dave, how can I extract useful information from the log? How can I replay it by one transaction? Perhaps it is possibly to find the trasaction which triggers the bug. I used `xfs_logprint -C` to save the log, but it is more than 100Mb. -- 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
