http://bugzilla.kernel.org/show_bug.cgi?id=12821 ------- Comment #1 from sandeen@xxxxxxxxxx 2009-03-05 09:26 ------- Is this something you can reproduce? I'm not remembering anything related offhand other than an early bug in the extent code, which I think should be fixed well before 2.6.27. If you find inode #2621457, I expect that it is very fragmented, and I'd guess that any access to it (reading it, that is, or perhaps extending it) will trip this error. If you can try a later kernel, maybe 2.6.27.x or 28.x or even .29 it'd let us know if the problem still exists; if not maybe there is more debugging we can do. Providing an e2image -r of the filesystem would also let us see what kind of layout that file has, though from your comments I'm guessing this may not be possible due to security reasons. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
