https://bugzilla.novell.com/show_bug.cgi?id=413732 User jason_miller@symantec.com added comment https://bugzilla.novell.com/show_bug.cgi?id=413732#c1 Summary: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:691: "transaction->t_updates == 0" Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jason_miller@symantec.com QAContact: kernel-maintainers@forge.provo.novell.com Found By: --- Created an attachment (id=231129) --> (https://bugzilla.novell.com/attachment.cgi?id=231129) syslog backtrace The kernel on an OpenSuSE 10.3 machine experienced an assertion failure, at which point all future I/O operations to at least one of the partitions on the machine blocked indefinitely. Jul 31 16:40:38 architect kernel: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:691: "transaction->t_updates == 0" The machine was (and normally is) under significant I/O load. Linux architect 2.6.22.18-0.2-default #1 SMP 2008-06-09 13:53:20 +0200 i686 i686 i386 GNU/Linux I've taken a look at the upstream kernel change logs, and it appears that this issue has already been fixed there: jbd: Fix assertion failure in fs/jbd/checkpoint.c http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=... A cursory glance at /usr/src/linux/fs/jbd/checkpoint.c on the affected system would appear to indicate that this hasn't been back-ported to the running kernel. The provided backtrace appears to confirm this as being the cause of the assertion failure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.