Lines Matching refs:enough

91 More recent filesystem designs contain enough redundancy in their metadata that
451 locked long enough to apply the update.
2397         leaf_load_factor = enough space ? default_load_factor : maxrecs
2404         node_load_factor = enough space ? default_load_factor : maxrecs
2615 If there are, the space metadata inconsistencies are reason enough to abort the
2621 enough information to fill a single inode chunk record, which is 64 consecutive
3116 long enough to check and correct the summary counters.
3282 enough to load it into the inode cache.
3619 1. Make sure the ondisk dquots are in good enough shape that all the incore
4113 The new log intent item contains enough information to track two logical fork
4229 - If both forks are in local format and the fork areas are large enough, the
4302 partitioned into ``log2(total rt extents)`` sections containing enough 32-bit
4711 during phase 3 to decide which files are corrupt enough to be zapped.
4881 inode chunks and then called bulkstat (``XFS_IOC_BULKSTAT``) to gather enough
4904 This doesn't completely solve the balancing problem, but reduces it enough to
4950 1. Start a round of repair with a workqueue and enough workers to keep the CPUs
5204 It is hoped that ``io_uring`` will pick up enough of this functionality that