Skip to content
Browse files

8373 TXG_WAIT in ZIL commit path

Reviewed by: Matthew Ahrens <>
Reviewed by: Prakash Surya <>
Approved by: Dan McDonald <>
  • Loading branch information...
avg-I authored and prakashsurya committed Jul 17, 2017
1 parent 2bee374 commit d28671a3b094af696bea87f52272d4c4d89321c7
Showing with 18 additions and 1 deletion.
  1. +18 −1 usr/src/uts/common/fs/zfs/zil.c
@@ -974,7 +974,24 @@ zil_lwb_write_start(zilog_t *zilog, lwb_t *lwb)
* to clean up in the event of allocation failure or I/O failure.
tx = dmu_tx_create(zilog->zl_os);
VERIFY(dmu_tx_assign(tx, TXG_WAIT) == 0);

* Since we are not going to create any new dirty data and we can even
* help with clearing the existing dirty data, we should not be subject
* to the dirty data based delays.
* We (ab)use TXG_WAITED to bypass the delay mechanism.
* One side effect from using TXG_WAITED is that dmu_tx_assign() can
* fail if the pool is suspended. Those are dramatic circumstances,
* so we return NULL to signal that the normal ZIL processing is not
* possible and txg_wait_synced() should be used to ensure that the data
* is on disk.
error = dmu_tx_assign(tx, TXG_WAITED);
if (error != 0) {
ASSERT3S(error, ==, EIO);
return (NULL);
dsl_dataset_dirty(dmu_objset_ds(zilog->zl_os), tx);
txg = dmu_tx_get_txg(tx);

0 comments on commit d28671a

Please sign in to comment.
You can’t perform that action at this time.