xfs/scrub/fscounters.c

27  * FS Summary Counters
33  * Then we compare what we computed against the in-core counters.
35  * However, the reality is that summary counters are a tricky beast to check.
46  * structures as quickly as it can.  We snapshot the percpu counters before and
64  * values, the percpu counters should be fairly close to each other.  However,
71  * contents and trust that the incore counters match the ondisk counters.  (The
73  * summary counters after checking all AG headers).  Do this from the setup
155  * that comprise the summary counters and compare them to the percpu counters.
229 	/* We must get the incore counters set up before we can proceed. */  in xchk_setup_fscounters()
236 	 * reduce the likelihood of background perturbations to the counters  in xchk_setup_fscounters()
290  * Calculate what the global in-core counters ought to be from the incore
291  * per-AG structure.  Callers can compare this to the actual in-core counters
292  * to estimate by how much both in-core and on-disk counters need to be
339 		 * Per-AG reservations are taken out of the incore counters,  in xchk_fscount_aggregate_agcounts()
355 	 * counters, so leave that out of the computation.  in xchk_fscount_aggregate_agcounts()
360 	 * Delayed allocation reservations are taken out of the incore counters  in xchk_fscount_aggregate_agcounts()
379 	 * counters while we were calculating things.  We'll try a few times  in xchk_fscount_aggregate_agcounts()
445  * Part 2: Comparing filesystem summary counters.  All we have to do here is
446  * sum the percpu counters and compare them to what we've observed.
496 /* Check the superblock counters. */
507 	/* Snapshot the percpu counters. */  in xchk_fscounters()
548 	 * something's probably wrong with the counters.  in xchk_fscounters()
553 	/* Walk the incore AG headers to calculate the expected counters. */  in xchk_fscounters()
566 	 * Compare the in-core counters with whatever we counted.  If the fs is  in xchk_fscounters()