Handle FLUSH errors as "expected"
Before #16061 zio_vdev_io_done() was not used for FLUSH requests. Addition of it triggers reprobe each TXG for vdevs not supporting them. Since those errors are often expected, they are normally handled by individual vdev drivers and should be ignored here. Signed-off-by: Alexander Motin <mav@FreeBSD.org> Sponsored by: iXsystems, Inc.
This commit is contained in:
parent
454c0b0e46
commit
be1795714b
|
@ -4114,7 +4114,8 @@ zio_vdev_io_done(zio_t *zio)
|
||||||
if (zio_injection_enabled && zio->io_error == 0)
|
if (zio_injection_enabled && zio->io_error == 0)
|
||||||
zio->io_error = zio_handle_label_injection(zio, EIO);
|
zio->io_error = zio_handle_label_injection(zio, EIO);
|
||||||
|
|
||||||
if (zio->io_error && zio->io_type != ZIO_TYPE_TRIM) {
|
if (zio->io_error && zio->io_type != ZIO_TYPE_FLUSH &&
|
||||||
|
zio->io_type != ZIO_TYPE_TRIM) {
|
||||||
if (!vdev_accessible(vd, zio)) {
|
if (!vdev_accessible(vd, zio)) {
|
||||||
zio->io_error = SET_ERROR(ENXIO);
|
zio->io_error = SET_ERROR(ENXIO);
|
||||||
} else {
|
} else {
|
||||||
|
|
Loading…
Reference in New Issue