Lines Matching full:hence

53 of reservation size limitations. Hence a rolling extent removal transaction
59 Hence it can be seen that the relogging operation is fundamental to the correct
84 IO permanently. Hence the XFS journalling subsystem can be considered to be IO
110 formatting the changes in a transaction to the log buffer. Hence we cannot avoid
127 being accumulated in memory. Hence the potential for loss of metadata on a
140 log is used effectively in many filesystems including ext3 and ext4. Hence
165 concurrent modification. Hence flushing the logical changes to the log would
192 Hence we avoid the need to lock items when we need to flush outstanding
236 Hence we need to keep the vector, but by attaching the memory buffer to it and
240 Hence we avoid needing a new on-disk format to handle items that have been
265 can we store state in any field that is protected by the AIL lock. Hence the
301 failure and an inconsistent filesystem and hence we must enforce the maximum
321 Hence a checkpoint has a context that tracks the state of the current
340 Hence log vectors need to be able to be chained together to allow them to be
427 written directly into the log buffers. Hence some other method of sequencing
529 rolling transactions for an example of this).  Hence we *must* always have
544 Hence we can grow the checkpoint transaction reservation dynamically as items
550 log. Hence as part of the reservation growing, we need to also check the size
573 buffers. Hence items that are relogged in the log buffers will have a pin count
604 (or not pinning, as the case may be). Hence we must hold the CIL flush/commit
784 Hence delayed logging should not introduce any constraints on log item