bf54da84fb
We're still seeing this test fail intermittently (that is, the clone happens), which must mean the write and the clone can still be happening on different txgs. It might be that there's still activity after the pool is created. So here we force a sync before starting the write. Sponsored-By: Klara Inc. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rob Norris <rob.norris@klarasystems.com> Closes #15359 |
||
|---|---|---|
| .. | ||
| block_cloning.kshlib | ||
| block_cloning_copyfilerange.ksh | ||
| block_cloning_copyfilerange_cross_dataset.ksh | ||
| block_cloning_copyfilerange_fallback.ksh | ||
| block_cloning_copyfilerange_fallback_same_txg.ksh | ||
| block_cloning_copyfilerange_partial.ksh | ||
| block_cloning_disabled_copyfilerange.ksh | ||
| block_cloning_disabled_ficlone.ksh | ||
| block_cloning_disabled_ficlonerange.ksh | ||
| block_cloning_ficlone.ksh | ||
| block_cloning_ficlonerange.ksh | ||
| block_cloning_ficlonerange_partial.ksh | ||
| cleanup.ksh | ||
| setup.ksh | ||