Lines Matching full:hence

56 of reservation size limitations. Hence a rolling extent removal transaction
62 Hence it can be seen that the relogging operation is fundamental to the correct
87 IO permanently. Hence the XFS journalling subsystem can be considered to be IO
113 formatting the changes in a transaction to the log buffer. Hence we cannot avoid
130 being accumulated in memory. Hence the potential for loss of metadata on a
143 log is used effectively in many filesystems including ext3 and ext4. Hence
169 concurrent modification. Hence flushing the logical changes to the log would
196 Hence we avoid the need to lock items when we need to flush outstanding
240 Hence we need to keep the vector, but by attaching the memory buffer to it and
244 Hence we avoid needing a new on-disk format to handle items that have been
270 can we store state in any field that is protected by the AIL lock. Hence the
307 failure and an inconsistent filesystem and hence we must enforce the maximum
327 Hence a checkpoint has a context that tracks the state of the current
346 Hence log vectors need to be able to be chained together to allow them to be
434 written directly into the log buffers. Hence some other method of sequencing
537 rolling transactions for an example of this).  Hence we *must* always have
552 Hence we can grow the checkpoint transaction reservation dynamically as items
558 log. Hence as part of the reservation growing, we need to also check the size
582 buffers. Hence items that are relogged in the log buffers will have a pin count
613 (or not pinning, as the case may be). Hence we must hold the CIL flush/commit
795 Hence delayed logging should not introduce any constraints on log item