Lines Matching full:disk

10 “important” data writes on-disk as quickly as possible. Once the important
11 data transaction is fully written to the disk and flushed from the disk write
14 final locations on disk (this could involve a lot of seeking or a lot of small
18 gets written through the journal to the disk. The effect of this is to
27 metadata are written to disk through the journal. This is slower but
29 disk before the metadata are written to disk through the journal.
46 middle of the disk.
48 All fields in jbd2 are written to disk in big-endian order. This is the
314      - This journal uses v2 of the checksum on-disk format. Each journal
319      - This journal uses v3 of the checksum on-disk format. This is the same as
391        should end up on disk.
401        should end up on disk. This is zero if JBD2_FEATURE_INCOMPAT_64BIT is
431      - On-disk block is escaped. The first four bytes of the data block just
457        should end up on disk.
477        should end up on disk.
512 In general, the data blocks being written to disk through the journal
525 journal replay after the file block was written to disk will cause
586 final locations on disk.
744 are submitted to the disk. In-progress transactions are waited upon and included