Lines Matching full:flushed
70 * the metaslab haven't had its changes flushed. During import, we use this
92 * metaslabs in-order from the oldest-flushed to the most recently flushed
94 * oldest flushed metaslab to distinguish which log space maps have become
109 * [1] The number of metaslabs that were last flushed on that TXG. This is
213 * flushed per txg) and that's why making it a percentage in terms of the
300 * spacemaps are not flushed and destroyed during export in order for the
407 * was flushed or destroyed (e.g due to device removal or pool export/destroy).
409 * We typically flush the oldest flushed metaslab so the first (and oldest)
456 * This function is called after a metaslab is flushed and typically that
457 * metaslab is the oldest flushed, which means that this function will
465 * Scenario [1]: It is possible that after we flushed the oldest flushed
469 * flushed metaslab was loading but we kept flushing more recently flushed
477 * Scenario [2]: The oldest flushed metaslab isn't necessarily accounted by
480 * removed, then the current oldest flushed metaslab could be accounted by an
497 * metaslabs in the pool as they all got flushed). Under this scenario we can't
794 * for this TXG's flushed metaslab count (aka sls_mscount which is in spa_flush_metaslabs()
836 * If this metaslab has been flushed this txg then we've done in spa_flush_metaslabs()
1100 * If we have already flushed entries for this TXG to this in spa_ld_log_sm_cb()
1399 "Prevent the log spacemaps from being flushed and destroyed "