search for: j_running_transaction

Hi Steven, Hi ext3-users list! We encountered a reproduceable problem with ext3: When issuing a FIBMAP ioctl for a block written right before while the FS is under high load (RH build universe), the assertion !journal->j_running_transaction fails at the bottom of journal_flush() in fs/jbd/journal.c. We encountered this problem with the arch=s390x (64 bit big endian) bootloader zipl, I'll try to reproduce it with 2.4.latest on arch=i386. I'll try to create a stack backtrace as well by inserting a BUG();. Strace of problem: ioc...

Hi all, We encountered a problem by chance today, a kernel bug which causes the following error: Assertion failure in journal_fl sh() at journal.c:1310: "!journal->j_running_transaction" kernel BUG at journal.c:1310! This happened while remounting an ext3 filesystem read-only. We often do this and haven't seen this bug before, so I suspect some kind of race. It appears to be related to a message posted to this list in January 2002 by Carsted Otte [https://listman.r...

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

Hi, On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote: > > I got the following error while rm'ing a 700mb file from an ext3 partition: > > Assertion failure in journal_unmap_buffer() at transaction.c:1857: > "transaction == journal->j_running_transaction" Hmm --- this is not one I think I've ever seen before. > >>EIP; c015ea1a <journal_unmap_buffer+fa/1b0> <===== > Trace; c015eb6e <journal_flushpage+9e/140> > Trace; c0156ae2 <ext3_flushpage+22/30> > Trace; c0125738 <do_flushpage+18/30> >...

...09:24:45 @@ -1834,6 +1834,7 @@ * running transaction if that is set, but nothing * else. */ JBUFFER_TRACE(jh, "on committing transaction"); + set_bit(BH_Freed, &bh->b_state); if (jh->b_next_transaction) { J_ASSERT(jh->b_next_transaction == journal->j_running_transaction);

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158