http://bugzilla.kernel.org/show_bug.cgi?id=11960 ------- Comment #1 from tytso@xxxxxxx 2008-11-05 12:55 ------- Note, -stable is a stale branch pointer. It reflects commits that Linus has pulled into mainline, so there's nothing _wrong_ with it, but it accidentally got published. You probably want either ext4-stable (which is the latest patches that have been accepted into mainline against the stable 2.6.27 kernel) or for-stable, which is a set of patches we're going to be sending to the 2.6.27.x kernel when I have a chance. It's almost certain that the bug won't show up in the ext4-stable branch, since in the latest mainline kernel we've dropped ext4_mb_poll_new_transaction and replaced it with something else that is far clearly. However, the code is still in the for-stable and 2.6.27.x branches, though. So if there is a bug in 2.6.27, we do want to track it down and fix it. Hmm... at a guess, looking at the symptoms, I suspect it happens when there are so many inodes on the orphaned inode list that it requries more than one transaction to clear all of the inoes on the orphaned inode list. How big is the journal on your filesystem? What does "dumpe2fs -h /dev/sdb1 | grep Journal" report? -- 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
