On Fri, Feb 05, 2010 at 10:43:10PM -0800, David Miller wrote: > From: Christian Kujau <li...@nerdbynature.de> > Date: Fri, 5 Feb 2010 22:28:47 -0800 (PST) > > > Hm, now it looks like this, but I don't know how it'd reveal more > > information: > > > > [ 210.707051] Kernel unaligned access at TPC[10101f18] > > btrfs_csum_final+0x38/0x60 [btrfs] > > [ 210.802236] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]] > > [ 210.874620] Kernel unaligned access at TPC[10101f18] > > btrfs_csum_final+0x38/0x60 [btrfs] > > [ 210.969899] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]] > > [ 228.724982] Kernel unaligned access at TPC[10101f18] > > btrfs_csum_final+0x38/0x60 [btrfs] > > [ 228.820220] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]] > > [ 228.892286] Kernel unaligned access at TPC[10101f18] > > btrfs_csum_final+0x38/0x60 [btrfs] > > [ 228.987851] Caller [10101f1c:btrfs_csum_final+0x3c/0x60 [btrfs]] > > > > I'm open for more patches :-) > > Confusing for me too. I'll try to think about this some more.
It is probably the directory code. I switched that to crc32c since you tried things. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
