On Tue, May 06, 2008 at 09:26:30AM +0200, Vegard Nossum wrote:
I posted a very similar problem a couple of days ago: http://www.nabble.com/BUG-in-ext3_sync_fs-td16999997.html to which I got zero replies. Can I close this in my internal bugzilla as dup/"not my fault"? The stacktrace looks very similar. This was also ext2 fs mounted (apparently) by ext3 code.
Yeah, sorry, I didn't have network access when I looked at your e-mail, and so I didn't see the stack trace until you pointed at the mail message again. Because you mentioned a USB stick, I assumed it was the problem with a USB stick getting pulled or being loose causing an I/O error leading to an oops problem, and I missed the hint of the problem occurring in the ext3 code when you were using an ext2 formattem. Fortunately when Geert reported the bug a second time, I was less dense at the time, and figured it out quickly. :-) - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
