2009/4/2 Alexander Beregalov <a.beregalov@xxxxxxxxx>: >>> > I'm helpless here. I don't see how we can miss a wakeup (plus you seem to >>> > be the only one reporting the bug). Could you please compile and test the kernel >>> > with the attached patch? It will print to kernel log when we go to sleep >>> > waiting for inode commit and when we send wakeups etc. When you hit the >>> > deadlock, please send me your kernel log. It should help with debugging why do >>> > we miss the wakeup. Thanks. >>> >>> Which patch? >> Ups. Forgot to attach ;). > > Cannot reproduce it on current 2.6.29-git. Strange. > It should already have all ext4/jbd2 patches from next-20090310, > but anyway it happened with 2.6.29-rc8 also. > I ran dbench in cycle on two indentical hosts for more than 24 hours > with no hang tasks. > > I will try 2.6.29. I cannot reproduce it with vanilla v2.6.29. It seems the problem has gone. Thanks Jan. The patch output: [133886.375874] JBD2: Waiting for ino 1062 [133886.376372] JBD2: Waking up sleeper on ino 1062 [133886.376824] JBD2: Woken on ino 1062 [134611.108451] JBD2: Waiting for ino 1102 [134611.108903] JBD2: Waking up sleeper on ino 1102 [134611.109787] JBD2: Woken on ino 1102 [134611.132912] JBD2: Waiting for ino 1074 [134611.133311] JBD2: Waking up sleeper on ino 1074 [134611.133707] JBD2: Woken on ino 1074 -- 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
