Lines Matching refs:transaction
11 data transaction is fully written to the disk and flushed from the disk write
70 - One transaction
73 Notice that a transaction begins with either a descriptor and some data,
74 or a block revocation list. A finished transaction always ends with a
76 transaction will be discarded during replay.
102 - One transaction
131 - The transaction ID that goes with this block.
145 written through the journal during a transaction.
148 transaction.
244 - Limit of journal blocks per transaction. (Not used?)
248 - Limit of data blocks per transaction. (Not used?)
437 - The data block was deleted by the transaction. (Not used?)
522 transaction. This is used to mark blocks that were journalled at one
530 mistakenly thought. Any block being added to a transaction will cause
559 revoked by this transaction. The size of each block number is 8 bytes if
583 The commit block is a sentry that indicates that a transaction has been
585 journal, the data stored with this transaction can be written to their
607 in the transaction. See jbd2_checksum_type_ for more info.
624 crc32 of all the blocks already written to the transaction.
628 - The time that the transaction was committed, in seconds since the epoch.
653 - Stores the TID of the transaction after which these fast commits should