Lines Matching refs:journal

12 how you decide to allocate the physical media on which the journal
15 for journal stored on a raw device (in a continuous range of blocks). A
21 journal file. The journalling layer expects the space for the journal
23 When loading the journal you must call jbd2_journal_load() to process
24 journal contents. If the client file system detects the journal contents
26 may call jbd2_journal_wipe() to clear the journal contents before
31 transactions in the journal and similarly jbd2_journal_load() will
38 You still need to actually journal your filesystem changes, this is done
40 the modification of each of the buffers with calls to the journal layer,
70 jbd2_journal_destroy() to clean up your in-core journal object.
72 Unfortunately there a couple of ways the journal layer can cause a
78 journal. Since transactions can't be nested/batched across differing
83 if there isn't enough space in the journal for your transaction (based
107 journal commit callback for this purpose.
109 With journal commit callbacks you can ask the journalling layer to call
113 ``journal->j_commit_callback`` function pointer and that function is
142 `journal->j_fc_cleanup_cb`: Cleanup function called after every full commit and
145 `journal->j_fc_replay_cb`: Replay function called for replay of fast commit
169 Using the journal is a matter of wrapping the different context changes,
190 The functions here are split into two groups those that affect a journal
196 .. kernel-doc:: fs/jbd2/journal.c
211 Tweedie <http://kernel.org/pub/linux/kernel/people/sct/ext3/journal-design.ps.gz>`__