search for: journal_unmap_buffer

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; c0156a...

...tion on disc is allocated to another file. If not, they might be flushed out to disc much later and overwrite something that has since been allocate the same location on disc. The pages are dealt with by truncate_inode_pages which ultimately calls journal_flushpage on each page which inturn calls journal_unmap_buffer. For data=writeback the data block will not be attached to the journal at all and the buffer is "Zapped" (marked as clean). For data=ordered the data block can only be dirty if it is part of the current transaction, or the committing transaction. (This is a consequence of the "ord...

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