Lines Matching refs:journal
362 * Validation Routine to verify that the TRIM list maintained by the journal
379 struct journal *jnl = (struct journal*)hfsmp->jnl;
417 ; being freed is passed to the journal code, and the extent will
620 ; written to the on-disk journal. This routine will add those
623 ; CAUTION: This routine is called while the journal's trim lock
630 ; CAUTION: If the journal becomes invalid (eg., due to an I/O
631 ; error when trying to write to the journal), this callback
633 ; the journal became invalid!
671 ; lingering in an uncommitted journal transaction. This may have data safety
672 ; implications. The intended use is to decide whether or not to force a journal flush
675 ; journal, resulting in data being overwritten if the transaction either
678 ; NOTE: This function assumes that the journal and catalog/extent locks are held.
722 /* Ask the journal if this extent overlaps with any pending TRIMs */
737 /* There may not be a journal. In that case, always return success. */
1079 * Last Resort: Find/use blocks that may require a journal flush.
1294 * In the journal case, we'll add the free extent once the journal
1300 * If the journal case, we'll only update sparseAllocation once the
1748 /* Otherwise, we looped around and couldn't find anything that wouldn't require a journal flush. */
2325 * that a journal flush might be appropriate. It's safe to
2326 * poke at the journal pointer here since we MUST have
2328 * If the journal is enabled, then it will have taken the requisite
2329 * journal locks. If it is not enabled, then we have taken
2514 * small, otherwise this can overflow journal transaction size
2516 * bitmap with relatively small journal).
2560 * overwhelm the journal.
3196 /* If there is no journal, go ahead and add to the free ext cache. */
3458 * The journal or allocation file lock must be held.
3481 * The journal or allocation file lock must be held.
4224 * table for the mount point. It should be done after any potential journal replays
4239 * list - journal trim list data structure for issuing TRIMs
4298 * When the journal replays blocks, it does so by writing directly to the disk