search for: journal_unlock_upd

...'ve been monitoring, have been experiencing. The other change I made, although it shouldn't affect the non-SMP system my kernel is running on, is to change the spin_unlock()/wait_event() to the prepare_to_wait()/spin_unlock()/schedule()/finish_wait() sequence, and move the wake_up() in journal_unlock_updates() from after the spin_unlock() to just before the lock is given up...I'm thinking the thread going to sleep needs to be put on the wait queue before the wake_up() occurs, or it could miss this wake_up(). All in all, I'm experiencing an unexpected delay in executing some ext3 file s...

...cks_per_page <Jun/27 03:57 pm>ext3: Unknown symbol journal_errno <Jun/27 03:57 pm>ext3: Unknown symbol journal_extend <Jun/27 03:57 pm>ext3: Unknown symbol journal_invalidatepage <Jun/27 03:57 pm>ext3: Unknown symbol journal_create <Jun/27 03:57 pm>ext3: Unknown symbol journal_unlock_updates <Jun/27 03:57 pm>ext3: Unknown symbol journal_revoke <Jun/27 03:57 pm>ext3: Unknown symbol journal_lock_updates <Jun/27 03:57 pm>ext3: Unknown symbol journal_start_commit <Jun/27 03:57 pm>ext3: Unknown symbol journal_flush <Jun/27 03:57 pm>ext3: Unknown symbol jour...

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other

I have ext3 0.0.6b + 2.2.19 and cannot get ext3 to compile as a module. If I try to modularize it, or turn in off completely, the kernel build fails. Is there an easy fix for this, or is there something that I am missing? Thanks. Peter