search for: t_journal

...access beyond end of device Mar 9 17:15:13 srck@trottelkunde 16:42: rw=0, want=0, limit=12289725 right before the bug(). this message didn't get parsed by ksymoops Mar 9 17:15:13 srck@trottelkunde Assertion failure in journal_start() at transaction.c:226: "handle->h_transaction->t_journal == journal" i'm somehow desperate by now, i get crashes like this on a monthly basis; the quota code always seems to be the cause... here are the lines of the last crashes (can't resolve call trace because the old kernels are gone and i didn't resolve the traces when they occured...

One of our servers (false) just oopsed. In the middle of lunch. Any advise? On console: false kernel: Assertion failure in journal_start() at transaction.c line 245: "handle->h_transaction->t_journal == journal" In kernel log (ran it through ksymoops): Nov 13 12:35:37 false kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Nov 13 12:35:37 false kernel: current->tss.cr3 = 00a2b000, %%cr3 = 00a2b000 Nov 13 12:35:37 false kernel: *pde = 00000000 Nov 13...

...ut cpu is 99% idle... after few minutes i cannot login again ... machine: pentium 200, 72 mb of ram, eide disks (brand new), dcom ethernet cards what's wrong? brane Jan 16 12:37:37 frost kernel: Assertion failure in journal_start() at transaction.c:225: "handle->h_transaction- >t_journal == journal" Jan 16 12:37:37 frost kernel: invalid operand: 0000 Jan 16 12:37:37 frost kernel: CPU: 0 Jan 16 12:37:38 frost kernel: EIP: 0010:[journal_start+79/208] Not tainted Jan 16 12:37:38 frost kernel: EIP: 0010:[<c015f7ef>] Not tainted Jan 16 12:37:38 frost kernel: EF...

...ition are 80 300Mb loopback file systems, formatted ext3. I got the following assertion yesterday which forced a lot of processes into D state. I'm not sure how easy it is to reproduce this problem. Assertion failure in journal_start() at transaction.c:226: "handle->h_transaction->t_journal == journal" The oops follows: invalid operand: 0000 CPU: 1 EIP: 0010:[<c0165908>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010292 eax: 0000006c ebx: c416d4e0 ecx: 00000086 edx: f7771f64 esi: d11cc000 edi: e9bd6be0 ebp: ca735600 esp...

...*commit_trans; + transaction_t *inode_trans, *commit_trans; int ret = 0; - if (!inode->i_transaction && !inode->i_next_transaction) + /* This is a quick check to avoid locking if not necessary */ + if (!jinode->i_transaction) goto out; - journal = inode->i_transaction->t_journal; + /* Locks are here just to force reading of recent values, it is + * enough that the transaction was not committing before we started + * a transaction adding the inode to orphan list */ spin_lock(&journal->j_state_lock); commit_trans = journal->j_committing_transaction; spin_un...

...*commit_trans; + transaction_t *inode_trans, *commit_trans; int ret = 0; - if (!inode->i_transaction && !inode->i_next_transaction) + /* This is a quick check to avoid locking if not necessary */ + if (!jinode->i_transaction) goto out; - journal = inode->i_transaction->t_journal; + /* Locks are here just to force reading of recent values, it is + * enough that the transaction was not committing before we started + * a transaction adding the inode to orphan list */ spin_lock(&journal->j_state_lock); commit_trans = journal->j_committing_transaction; spin_un...

...d after then it looks, like it's in normal operation again. the only problem is load, which is incrementing constantly, but cpu is 99% idle... what's wrong? brane Jan 16 12:37:37 frost kernel: Assertion failure in journal_start() at transaction.c:225: "handle->h_transaction- >t_journal == journal" Jan 16 12:37:37 frost kernel: invalid operand: 0000 Jan 16 12:37:37 frost kernel: CPU: 0 Jan 16 12:37:38 frost kernel: EIP: 0010:[journal_start+79/208] Not tainted Jan 16 12:37:38 frost kernel: EIP: 0010:[<c015f7ef>] Not tainted Jan 16 12:37:38 frost kernel: EF...

Hi! I experienced an ext3 crash a few days ago, the corresponding part of my kernel log is attached (there were no IDE-errors, just the ext3 stuff). The /home partition (/dev/hdd2) got remounted ro, so the box was still usable somehow (was able to log in, kill stuff and reboot it). I rebooted it, it came back up again w/o any problems, remounted /home ro and did a e2fsck on it, which reported

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

...{ + journal_unfile_buffer(bh); + bh->b_transaction = NULL; + if (bh->b_cp_transaction) + journal_remove_checkpoint(bh); + } else if (!buffer_locked(bh) && !buffer_dirty(bh)) { journal_unfile_buffer(bh); bh->b_transaction = NULL; unlock_journal(transaction->t_journal); -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert

...*commit_trans; + transaction_t *inode_trans, *commit_trans; int ret = 0; - if (!inode->i_transaction && !inode->i_next_transaction) + /* This is a quick check to avoid locking if not necessary */ + if (!jinode->i_transaction) goto out; - journal = inode->i_transaction->t_journal; + /* Locks are here just to force reading of recent values, it is + * enough that the transaction was not committing before we started + * a transaction adding the inode to orphan list */ spin_lock(&journal->j_state_lock); commit_trans = journal->j_committing_transaction; spin_un...

Hello Since 2.4.20, we have problems with ext3. Machine is 2xPentium III (1GHz), 2GB RAM, 1GB swap. RH 8.0 (glibc-2.3.1-21), gcc (GCC) 3.2 20020903 We have a lot of users: oceanic:~# wc -l /etc/passwd 6694 /etc/passwd connected via SAMBA (2.2.7) from 200-300 Windows-XX workstations Partition with ext3 looks like this: oceanic:~# mount |grep ext3 /dev/sdb5 on /home1 type ext3

...*commit_trans; + transaction_t *inode_trans, *commit_trans; int ret = 0; - if (!inode->i_transaction && !inode->i_next_transaction) + /* This is a quick check to avoid locking if not necessary */ + if (!jinode->i_transaction) goto out; - journal = inode->i_transaction->t_journal; + /* Locks are here just to force reading of recent values, it is + * enough that the transaction was not committing before we started + * a transaction adding the inode to orphan list */ spin_lock(&journal->j_state_lock); commit_trans = journal->j_committing_transaction; spin_un...

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

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