From 21df134f4cb1c1e05eb89992b71573843df62b27 Mon Sep 17 00:00:00 2001 From: sanjeevbagewadi Date: Fri, 11 Aug 2017 04:23:40 +0530 Subject: zio_dva_throttle_done() should allow zinjected ZIO If fault injection is enabled, the ZIO_FLAG_IO_RETRY could be set by zio_handle_device_injection() to generate the FMA events and update stats. Hence, ignore the flag and process such zios. A better fix would be to add another flag in the zio_t to indicate that the zio is failed because of a zinject rule. However, considering the fact that we do this in debug bits, we could do with the crude check using the global flag zio_injection_enabled which is set to 1 when zinject records are added. Reviewed-by: Brian Behlendorf Signed-off-by: Sanjeev Bagewadi Closes #6383 Closes #6384 --- module/zfs/zio.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'module') diff --git a/module/zfs/zio.c b/module/zfs/zio.c index 82e801e83..1d69d8d8d 100644 --- a/module/zfs/zio.c +++ b/module/zfs/zio.c @@ -3661,7 +3661,8 @@ zio_dva_throttle_done(zio_t *zio) ASSERT3U(zio->io_child_type, ==, ZIO_CHILD_VDEV); ASSERT(vd != NULL); ASSERT3P(vd, ==, vd->vdev_top); - ASSERT(!(zio->io_flags & (ZIO_FLAG_IO_REPAIR | ZIO_FLAG_IO_RETRY))); + ASSERT(zio_injection_enabled || !(zio->io_flags & ZIO_FLAG_IO_RETRY)); + ASSERT(!(zio->io_flags & ZIO_FLAG_IO_REPAIR)); ASSERT(zio->io_flags & ZIO_FLAG_IO_ALLOCATING); ASSERT(!(lio->io_flags & ZIO_FLAG_IO_REWRITE)); ASSERT(!(lio->io_orig_flags & ZIO_FLAG_NODATA)); -- cgit v1.2.3