Lines Matching refs:journal

8 To guarantee write atomicity, the dm-integrity target uses journal, it
9 writes sector data and integrity tags into a journal, commits the journal
53 	D - direct writes (without journal) - in this mode, journaling is
58 		journal and atomicity is guaranteed. In case of crash,
62 	R - recovery mode - in this mode, journal is not replayed,
73 	The size of journal, this argument is used only if formatting the
91 	The journal watermark in percents. When the size of the journal
92 	exceeds this watermark, the thread that flushes the journal will
96 	Commit time in milliseconds. When this time passes, the journal is
97 	written. The journal is also written immediatelly if the FLUSH
121 	Encrypt the journal using given algorithm to make sure that the
122 	attacker can't read the journal. You can use a block cipher here
126 	The journal contains history of last writes to the block device,
127 	an attacker reading the journal could see the last sector nubmers
130 	situation, you can encrypt the journal.
133 	Protect sector numbers in the journal from accidental or malicious
139 	mode, the integrity of journal entries is checked when replaying
140 	the journal. Thus, modified sector number would be detected at
149 The journal mode (D/J), buffer_sectors, journal_watermark, commit_time can
165 	* the number of journal sections
171 * journal
172 	The journal is divided into sections, each section contains:
173 	* metadata area (4kiB), it contains journal entries
174 	  every journal entry contains:
182 		  numbers in the journal section, to protect against a
184 		  numbers in the journal.
186 	* data area (the size is variable; it depends on how many journal
190 		  the journal entry)
192 	To test if the whole journal section was written correctly, every
193 	512-byte sector of the journal ends with 8-byte commit id. If the
194 	commit id matches on all sectors in a journal section, then it is