Bug 11960
Summary: | Oops in ext4_mb_poll_new_transaction | ||
---|---|---|---|
Product: | File System | Reporter: | Kelly Kane (kelly) |
Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
Status: | RESOLVED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | tytso |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Kelly Kane
2008-11-05 09:34:06 UTC
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? backup:~# dumpe2fs -h /dev/sdb1 | grep Journal dumpe2fs 1.41.3 (12-Oct-2008) Journal inode: 8 Journal backup: inode blocks Journal size: 128M I'll work on building a new kernel with the actual stable stuff soon. Hopefully we won't see it there! OK, if you had a 128megs journal, it must have been a corrupted orphan list and/or journal that caused the crash. That's consistent with the I'd really like to be able to create a reproduction case for this, since otherwise we won't know if the problem has been fixed in the newer mainline kernel. Any updates on this bug? If not, given that the function in question is no longer in the ext4 codebase, I plan to close this bug. Thanks!! There haven't been any updates since November 2008, and the function in question no longer is in the ext4 code base. Please file a new bug if you are still seeing problems. Thanks!! |