> So we also need a "txg dirty" or similar > property to be exposed from the kernel.
Or not.. if you find this condition, defer, but check again in a minute (really, after a full txg_interval has passed) rather than on the next scheduled snapshot. on that next check, if the txg has advanced again, snapshot. if not, defer until the next scheduled snapshot as usual. Yes, the txg may now be dirty this second time around - but it's after the snapshot was due, so these writes will be collected in the next snapshot. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
