George Wilson 7d2489cfad nopwrites on dmu_sync-ed blocks can result in a panic ... After device removal, performing nopwrites on a dmu_sync-ed block will result in a panic. This panic can show up in two ways: 1. an attempt to issue an IOCTL in vdev_indirect_io_start() 2. a failed comparison of zio->io_bp and zio->io_bp_orig in zio_done() To resolve both of these panics, nopwrites of blocks on indirect vdevs should be ignored and new allocations should be performed on concrete vdevs. Reviewed-by: Igor Kozhukhov <igor@dilos.org> Reviewed-by: Pavel Zakharov <pavel.zakharov@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Don Brady <don.brady@delphix.com> Signed-off-by: George Wilson <gwilson@delphix.com> Closes #8957		2019-09-25 11:27:48 -07:00
..
callbacks	ZTS: change $(cat) to $(<) for speedup	2018-10-31 12:00:06 -05:00
cmd	Use sigaction(2) instead of sigset(3) for portability	2019-04-30 20:45:17 -07:00
include	ZTS: Fix mmp_interval failure	2019-09-25 11:27:47 -07:00
tests	nopwrites on dmu_sync-ed blocks can result in a panic	2019-09-25 11:27:48 -07:00
Makefile.am	OpenZFS 7503 - zfs-test should tail ::zfs_dbgmsg on test failure	2017-04-12 13:36:48 -07:00