Lines Matching refs:journal

160 how you decide to allocate the physical media on which the journal
163 for journal stored on a raw device (in a continuous range of blocks). A
169 journal file. The journalling layer expects the space for the journal
171 When loading the journal you must call :c:func:`jbd2_journal_load` to process
172 journal contents. If the client file system detects the journal contents
174 may call :c:func:`jbd2_journal_wipe` to clear the journal contents before
179 transactions in the journal and similarly :c:func:`jbd2_journal_load` will
186 You still need to actually journal your filesystem changes, this is done
188 the modification of each of the buffers with calls to the journal layer,
218 :c:func:`jbd2_journal_destroy` to clean up your in-core journal object.
220 Unfortunately there a couple of ways the journal layer can cause a
226 journal. Since transactions can't be nested/batched across differing
231 if there isn't enough space in the journal for your transaction (based
255 journal commit callback for this purpose.
257 With journal commit callbacks you can ask the journalling layer to call
261 ``journal->j_commit_callback`` function pointer and that function is
286 Using the journal is a matter of wrapping the different context changes,
307 The functions here are split into two groups those that affect a journal
313 .. kernel-doc:: fs/jbd2/journal.c
328 Tweedie <http://kernel.org/pub/linux/kernel/people/sct/ext3/journal-design.ps.gz>`__